• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Again problems with my nameservers....

T

thastudio

Guest
Hello

I have problems with my nameservers, and I don't know what I am doing wrong...

My DNS settings for the domainname with the nameservers:
thastudio.be. NS ns1.thastudio.be.
thastudio.be. NS ns2.thastudio.be.
thastudio.be. NS ns3.thastudio.be.
thastudio.be. A 213.148.255.64
webmail.thastudio.be. A 213.148.255.64
mail.thastudio.be. A 213.148.255.64
ns1.thastudio.be. A 213.148.255.64
ns2.thastudio.be. A 213.148.255.65
ns3.thastudio.be. A 213.148.255.66
ftp.thastudio.be. CNAME thastudio.be.
www.thastudio.be. CNAME thastudio.be.
*.thastudio.be. CNAME thastudio.be.
thastudio.be. MX (10) mail.thastudio.be.
thastudio.be. MX (20) esli.wesowe-is.nl.
213.148.255.64 / 24 PTR thastudio.be.
213.148.255.65 / 24 PTR thastudio.be.
213.148.255.66 / 24 PTR thastudio.be.
thastudio.be. TXT "v=spf1 a ptr ip4:213.148.255.64/24, ip4:213.148.255.65/24, ip4:213.148.255.66/24 ~all"

The DNS settings for one of my clients:
blueolive.be. NS ns1.thastudio.be.
blueolive.be. NS ns2.thastudio.be.
blueolive.be. NS ns3.thastudio.be.
blueolive.be. A 213.148.255.65
webmail.blueolive.be. A 213.148.255.65
mail.blueolive.be. A 213.148.255.65
ftp.blueolive.be. CNAME blueolive.be.
www.blueolive.be. CNAME blueolive.be.
*.blueolive.be. CNAME blueolive.be.
blueolive.be. MX (10) mail.blueolive.be.
blueolive.be. MX (20) esli.wesowe-is.nl.
blueolive.be. TXT "v=spf1 a ptr ip4:213.148.255.64/24, ip4:213.148.255.65/24, ip4:213.148.255.66/24 ~all"

The results from dnsreport.com:
Thastudio.be
Blueolive.be

The settings in the whois of thastudio.be:
ns1.thastudio.be -> 213.148.255.64
ns2.thastudio.be -> 213.148.255.65
ns3.thastudio.be -> 213.148.255.66

What am I doing wrong?


Thanks in advance
 
Doing a DNS lookup on ns3.thastudio.be, I am getting:

Searching for ns3.thastudio.be A record at ns1.thastudio.be. [213.148.255.64]: Reports that no A records exist. [took 98 ms]

So for some reason, even though you posted that you have an A record for ns3 with the proper IP address, it is not responding to the request with the IP.

If I do a 'dig @ns1.thastudio.be ns3.thastudio.be', I am getting no ANSWER section. But if I do 'dig @ns1.thastudio.be ns2.thastudio.be', I am getting an ANSWER section:

;ns2.thastudio.be. 86400 IN A 213.148.255.65

Your server is responding to requests to ns1 and ns2, so we know your bind/named service is running.

You may have to manually check the contents of the zone file for this domain. It should be located at:

/var/named/run-root/var/thastudio.be

Check your /etc/named.conf file and make sure you have not specified any 'listen on' option. If you do specify, then you must list all 3 IPs. If the option is not present or is commented out, then bind/named should listen on all IPs available.

That's all I can think of at the moment.
 
In my /etc/named.conf everything is correct, and the content for my /etc/hosts is:
213.148.255.64 sunrise.wesowe-is.nl


Thanks in advance
 
Originally posted by jamesyeeoc
You may have to manually check the contents of the zone file for this domain. It should be located at:

/var/named/run-root/var/thastudio.be

I can't find this file, i use Plesk 7.5.3. Maybe the location of this file is changed?
 
Login to the server using SSH, Issue the following command at a shell prompt:

ps -ax |grep 'named'

You should see something like:

31879 ? S 0:00 /usr/sbin/named -u named -c /etc/named.conf -u named -t /var/named/run-root

The last part will tell you the base folder for the var/thastudio.be zone file

(I checked this on a 7.5.3 test server, OS = RH)

What OS are you using?
 
I use FreeBSD and get the following result in the thastudio.be file:
$TTL 86400

@ IN SOA ns1.thastudio.be. hosting.thastudio.net. (
1121386997 ; Serial
10800 ; Refresh
3600 ; Retry
604800 ; Expire
86400 ) ; Minimum

thastudio.be. IN NS ns1.thastudio.be.
thastudio.be. IN NS ns2.thastudio.be.
thastudio.be. IN NS ns3.thastudio.be.
thastudio.be. IN A 213.148.255.64
webmail.thastudio.be. IN A 213.148.255.64
mail.thastudio.be. IN A 213.148.255.64
ns1.thastudio.be. IN A 213.148.255.64
ns2.thastudio.be. IN A 213.148.255.65
ns3.thastudio.be. IN A 213.148.255.66
ftp.thastudio.be. IN CNAME thastudio.be.
www.thastudio.be. IN CNAME thastudio.be.
*.thastudio.be. IN CNAME thastudio.be.
thastudio.be. IN MX 10 mail.thastudio.be.
thastudio.be. IN MX 20 esli.wesowe-is.nl.
thastudio.be. IN TXT "v=spf1 a ptr ip4:213.148.255.64/24, ip4:213.148.255.65/24, ip4:213.148.255.66/24 ~all"

BTW, it was located on /usr/local/psa/named/run-root/var/thastudio.be
 
Path diffs between OS's is common, I sometimes forget to stipulate that my posts are based on RH distros.... :)

Your file contents relating to the NSx entries appear to be fine.

Did you 'register' the ns3 nameserver and IP at your Domain Registrar (NetSol, GoDaddy, etc)??

Have you tried restarting the bind/named service (don't know the FreeBSD command for that) or restarting the server itself?

At the shell prompt, what do you get if you give the command:

dig @ns3.thastudio.be www.thastudio.be

?
 
Now I did it both: restarted the BIND service and restarted the server...

When I dig after ns3.thastudio.be I get:
;; global options: printcmd
;; connection timed out; no servers could be reached

And if I dig after ns2.thastudio.be I get:
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43544
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;www.thastudio.be. IN A

;; ANSWER SECTION:
www.thastudio.be. 86400 IN CNAME thastudio.be.
thastudio.be. 86400 IN A 213.148.255.64

;; AUTHORITY SECTION:
thastudio.be. 86400 IN NS ns1.thastudio.be.
thastudio.be. 86400 IN NS ns2.thastudio.be.

;; ADDITIONAL SECTION:
ns1.thastudio.be. 86400 IN A 213.148.255.64
ns2.thastudio.be. 86400 IN A 213.148.255.65

;; Query time: 2 msec
;; SERVER: 213.148.255.65#53(ns2.thastudio.be)
;; WHEN: Fri Jul 15 11:53:54 2005
;; MSG SIZE rcvd: 132
 
Right, so what that means is that the server which *should* be responding as ns3 is not responding to DNS requests.

Are all 3 of your IPs on the same server? If they are, then did you check named.conf for the presence of the Listen On option? (as I posted earlier)
 
I will post the full file when my server is back on-line.
But when I looked earlier this day every domainname had the three IP's standing with it, so I think this is correct.

But in a few minutes I post the full file...
 
Regarding the 3 IPs, I am not referring to if they were listed in all the domain's DNS entries.

Have you made sure that all 3 IP addresses are defined in the OS network interfaces files, AND that all 3 IPs are being responded to by the server?? (like a ping test from a different machine)
 
The 3 IP's are in my IP pool, and untill my reboot I could do a ping to them all from my PC...

But now the reboot is taking very long :-s
 
Rebooting taking a long time, ok, I guess you have some investigation to do. If or when it finally boots up, check ALL your log files for indications of where the problems may be:

OS specific (see your OS docs)
Plesk: /usr/local/psa/admin/logs
Plesk: /usr/local/psa/var/logs

also if they exist:

/var/log

Good luck, and good night for now
 
After serveral tries my server wouldn't start again. My provider couldn't make a connection from the internal network so the server is really dead on this moment.

I had the choice: get remote hands straightaway and pay for it or wait untill next tuesday and let him check for free.

So now I have chosen for the second option.
But is it possible that this problem of restarting my server also is the same problem for my nameservers?

I know nobody can answer this for 100% sure but is there a possibility or not? And I will post the results tuesday after reading my logs...

Thanks for the tips you allready gave me...
 
Back
Top