The Planet Forums > A little help to see what I missed (DNS Setup)

ZeusChicago

Oct 6 2006, 11:15 AM

Ok. I have a new server I am setting up and trying to gete nameserver services working properly.

RHE4 / w Cpanel

The domain itself is registerd through orbit via theplanet

Hostname: zeus.almightyservices.com
Nameserver1 : ns1.almightyservices.com
(registred as nameserver through orbit)
(registred as A record through orbit)

Nameserver2 : ns2.almightyservices.com
(registred as nameserver through orbit)
(registred as A record through orbit)

Both have a unique IP address(s) that I have reserved for each of the nameserver and have configred them via Cpanel.

I have setup the Nameserver services in cpanel and they appear to be up and running. Zone files are up for my main domain (almightyservices.com) and I added a my host and name servers to the zone file.

After all that, I had a new URL registred (in orbit). Edited the name servers for that domain to be ns1.almightyservices.com and ns2.almightyservices.com

Waited 48 hours and using the DNS tools from I get the following when testing the domain records
http://www.dnsstuff.com

QUOTE

Searching for slickksports.com A record at l.root-servers.net Got referral to B.GTLD-SERVERS.NET. [took 74 ms]
Searching for slickksports.com A record at B.GTLD-SERVERS.NET. Got referral to ns1.almightyservices.com. [took 221 ms]
Searching for slickksports.com A record at ns1.almightyservices.com. Timed out. Trying again.
Searching for slickksports.com A record at ns1.almightyservices.com. Timed out. Trying again.
Searching for slickksports.com A record at ns2.almightyservices.com. Timed out. Trying again.
Searching for slickksports.com A record at ns2.almightyservices.com. Timed out. Trying again.
Searching for slickksports.com A record at ns2.almightyservices.com. Timed out. Trying again.
Searching for slickksports.com A record at ns2.almightyservices.com. Timed out. Trying again.

gbock

Oct 6 2006, 11:14 PM

CODE

[gbock gbock]$ whois almightyservices.com | grep NS

NS2.THEPLANETDOMAINS.COM 216.185.109.13

NS1.THEPLANETDOMAINS.COM 216.185.113.11

It looks like the glue records have not updated.

CODE

[gbock gbock]$ dig +trace ns1.almightyservices.com @4.2.2.1

; <<>> DiG 9.2.4 <<>> +trace ns1.almightyservices.com @4.2.2.1
; (1 server found)
;; global options: printcmd

. 31406 IN NS I.ROOT-SERVERS.NET.

. 31406 IN NS J.ROOT-SERVERS.NET.

. 31406 IN NS K.ROOT-SERVERS.NET.

. 31406 IN NS L.ROOT-SERVERS.NET.

. 31406 IN NS M.ROOT-SERVERS.NET.

. 31406 IN NS A.ROOT-SERVERS.NET.

. 31406 IN NS B.ROOT-SERVERS.NET.

. 31406 IN NS C.ROOT-SERVERS.NET.

. 31406 IN NS D.ROOT-SERVERS.NET.

. 31406 IN NS E.ROOT-SERVERS.NET.

. 31406 IN NS F.ROOT-SERVERS.NET.

. 31406 IN NS G.ROOT-SERVERS.NET.

. 31406 IN NS H.ROOT-SERVERS.NET.
;; Received 228 bytes from 4.2.2.1#53(4.2.2.1) in 2 ms

com. 172800 IN NS F.GTLD-SERVERS.NET.

com. 172800 IN NS G.GTLD-SERVERS.NET.

com. 172800 IN NS H.GTLD-SERVERS.NET.

com. 172800 IN NS I.GTLD-SERVERS.NET.

com. 172800 IN NS J.GTLD-SERVERS.NET.

com. 172800 IN NS K.GTLD-SERVERS.NET.

com. 172800 IN NS L.GTLD-SERVERS.NET.

com. 172800 IN NS M.GTLD-SERVERS.NET.

com. 172800 IN NS A.GTLD-SERVERS.NET.

com. 172800 IN NS B.GTLD-SERVERS.NET.

com. 172800 IN NS C.GTLD-SERVERS.NET.

com. 172800 IN NS D.GTLD-SERVERS.NET.

com. 172800 IN NS E.GTLD-SERVERS.NET.
;; Received 498 bytes from 192.36.148.17#53(I.ROOT-SERVERS.NET) in 136 ms

ns1.almightyservices.com. 172800 IN A 70.84.185.142

almightyservices.com. 172800 IN NS ns1.theplanetdomains.com.

almightyservices.com. 172800 IN NS ns2.theplanetdomains.com.
;; Received 175 bytes from 192.35.51.30#53(F.GTLD-SERVERS.NET) in 54 ms

dnsreports.com seems to be fine at the moment: http://www.dnsreport.com/tools/dnsreport.c...htyservices.com

Did you change the ns servers back to ours?

ZeusChicago

Oct 13 2006, 01:27 PM

The Almightyservices.com domain itself uses theplanet as its DNS.

I have registered the domain slickksports.com with the planet as well and configured the DNS servers for this domain to be ns1.almightyservices.com and ns2.almightyservices.com

When I do a DNS report however
http://www.dnsreport.com/tools/dnsreport.c...lickksports.com

QUOTE

PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:

ns1.almightyservices.com. [70.84.185.142] [TTL=172800] [US]
ns2.almightyservices.com. [70.84.185.141] [TTL=172800] [US]

[These were obtained from g.gtld-servers.net]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.

PASS Glue at parent nameservers OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.
PASS DNS servers have A records OK. All your DNS servers either have A records at the zone parent servers, or do not need them (if the DNS servers are on other TLDs). A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers. Note that there will be problems if your DNS servers do not have these same A records.

NS FAIL NS A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox, it's due to a bug in their DNS Proxy, which must be disabled (31 Jul 2006 UPDATE: several years after being informed of this, there is a rumor that there is a fix that allows the Watchguard DNS proxy to work).

ZeusChicago

Oct 13 2006, 01:30 PM

i.e. if you try to do a nslookup on slickksports.com you will get a timeout from ns1.almightyservices.com and ns2.almightyservices.com

Its like everything is working right until the very end (of course). Been pulling my hair out. Its not an emergency because I usually just edit the zone files of customers pointing to my server anyway, but having grown from 4-5 to 50 clients, thats getting really old at this point

ZeusChicago

Oct 13 2006, 01:54 PM

while troubleshooting another issue I ran into this, and i think it might be the cause. I'm not a unix expert, but it looks like the additional IP's given to me by theplanet are not pointing to the correct network card (I think mine is Eth1 , not Eth0. The two nameserver IP's are in the list below.

I got the following error when stoping then starting ipaliases. Could this be my problem and does anyone know the file I have to edit to correct the nic its pointing at?

QUOTE

root@zeus [/etc]# /etc/rc.d/init.d/ipaliases start
Bringing up eth0:1 [ OK ]
Routing 70.84.185.131 SIOCADDRT: No such device
[FAILED]
Bringing up eth0:2 [ OK ]
Routing 70.84.185.132 SIOCADDRT: No such device
[FAILED]
Bringing up eth0:3 [ OK ]
Routing 70.84.185.133 SIOCADDRT: No such device
[FAILED]
Bringing up eth0:4 [ OK ]
Routing 70.84.185.134 SIOCADDRT: No such device
[FAILED]
Bringing up eth0:5 [ OK ]
Routing 70.84.185.135 SIOCADDRT: No such device
[FAILED]
Bringing up eth0:6 [ OK ]
Routing 70.84.185.136 SIOCADDRT: No such device
[FAILED]
Bringing up eth0:7 [ OK ]
Routing 70.84.185.137 SIOCADDRT: No such device
[FAILED]
Bringing up eth0:8 [ OK ]
Routing 70.84.185.138 SIOCADDRT: No such device
[FAILED]
Bringing up eth0:9 [ OK ]
Routing 70.84.185.139 SIOCADDRT: No such device
[FAILED]
Bringing up eth0:10 [ OK ]
Routing 70.84.185.140 SIOCADDRT: No such device
[FAILED]
Bringing up eth0:11 [ OK ]
Routing 70.84.185.141 SIOCADDRT: No such device
[FAILED]
Bringing up eth0:12 [ OK ]
Routing 70.84.185.142 SIOCADDRT: No such device
[FAILED]

knicholson

Oct 13 2006, 08:41 PM

Zeus,

You are correct, your particular server uses eth1 as its main Ethernet device. cPanel assumes its eth0 by default, so when you had added your additional IPs via the WHM interface it bound them to eth0.

To correct this, in WHM go to Basic cPanel/WHM Setup, set Alternate Main Ethernet Device to eth1, and then click save.

Then, log in via ssh as root and restart ipaliases with the command:

/etc/rc.d/init.d/ipaliases restart

Your additional IPs should then work properly.

ZeusChicago

Oct 13 2006, 11:59 PM

QUOTE (knicholson)

Zeus,

You are correct, your particular server uses eth1 as its main Ethernet device. cPanel assumes its eth0 by default, so when you had added your additional IPs via the WHM interface it bound them to eth0.

To correct this, in WHM go to Basic cPanel/WHM Setup, set Alternate Main Ethernet Device to eth1, and then click save.

Then, log in via ssh as root and restart ipaliases with the command:

/etc/rc.d/init.d/ipaliases restart

Your additional IPs should then work properly.

Problem Fixed!

You are my favorite person today!

Go ahead and take the rest of the day off, when you see this, tell your boss your I approved it