PDA

View Full Version : Problem with IPs on new dedicated server


eBizAlive
05-26-03, 11:16 AM
I hope that someone will take the time to read this and lend me a helping hand. I am stuck with this problem and don't know what to do.

This issue has been going on for days now. I created a reseller account with private nameservers and IPs for this client, but for some reasons his nameservers doesn't work - or I don't know if it is one of these situations with propagation that takes days.

When I test it on

http://www.ip-plus.net/tools/dns_check_set.en.html

domain.com
IP for NS1 xx.xx.xxx.xx

it returns this error:

check-dom domain.com IP for NS1

Setting Source IP Address to : "164.128.36.54"

Check if the server "xx.xx.xxx.xx" is configured for "domain.com" ... failed.
*** ERROR *** domain.com SOA record not found at xx.xx.xxx.xx, try again

Testing domain.com at dnsreport.com returns an error as well. It only returns the first category 'Parent' which passes but an error is returned at the next category 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.

The client can access his WHM/cPanel using the IP without any problem and I did several successfull traceroutes to both IPs (ns1/ns2) from traceroute.org.

So I can't figure this one out. Does anybody here have experience with a similar situation or can tell me why this account won't work?

This is a new server that were added to an existing trust relationship as a slave. Several accounts has already been set up namebased on it, using anonymous nameservers (no ded. IPs) and they're working without any problems. This is the first account set up with private nameservers and dedicated IPs on this server.

Hope that someone here have the answer or could lead me in the right direction. Several support techs has looked at it but noone could figure it out until now.

Thanks
John

allan
05-27-03, 10:16 AM
It sounds like the nameservers do not actually have any information for the domain. Although, I don't know this for sure -- if you provide me with the domain name, I can test this theory for sure (if you don't want to make the domain public, feel free to PM it to me).

eBizAlive
05-27-03, 11:53 AM
Thanks Allan, the domain is rionegocios.com

John

allan
05-27-03, 12:09 PM
Okay, the two authoritative nameservers for rionegocios.com are:


Domain servers in listed order:
NS1.RIONEGOCIOS.COM 69.22.163.35
NS2.RIONEGOCIOS.COM 69.22.163.36


Are those the correct IP Addresses?

Both of those IP Addresses do respond to pings:


vbind.com /home/allan#ping 69.22.163.35
PING 69.22.163.35 (69.22.163.35) from 66.150.197.45 : 56(84) bytes of data.
64 bytes from 69.22.163.35: icmp_seq=0 ttl=48 time=70.054 msec
64 bytes from 69.22.163.35: icmp_seq=1 ttl=48 time=70.563 msec

vbind.com /home/allan#ping 69.22.163.36
PING 69.22.163.36 (69.22.163.36) from 66.150.197.45 : 56(84) bytes of data.
64 bytes from 69.22.163.36: icmp_seq=0 ttl=48 time=70.168 msec
64 bytes from 69.22.163.36: icmp_seq=1 ttl=48 time=70.411 msec
64 bytes from 69.22.163.36: icmp_seq=2 ttl=48 time=69.979 msec


BUT, neither appears to be running DNS software:


vbind.com /home/allan#dig @69.22.163.35 version.bind chaos txt

; <<>> DiG 9.2.1 <<>> @69.22.163.35 version.bind chaos txt
;; global options: printcmd
;; connection timed out; no servers could be reached
vbind.com /home/allan#dig @69.22.163.36 version.bind chaos txt

; <<>> DiG 9.2.1 <<>> @69.22.163.36 version.bind chaos txt
;; global options: printcmd
;; connection timed out; no servers could be reached


And, in case you are running something other than BIND:


vbind.com /home/allan#dig @69.22.163.35 RIONEGOCIOS.COM SOA

; <<>> DiG 9.2.1 <<>> @69.22.163.35 RIONEGOCIOS.COM SOA
;; global options: printcmd
;; connection timed out; no servers could be reached


vbind.com /home/allan#dig @69.22.163.36 RIONEGOCIOS.COM SOA

; <<>> DiG 9.2.1 <<>> @69.22.163.36 RIONEGOCIOS.COM SOA
;; global options: printcmd
;; connection timed out; no servers could be reached



So, it appears that the DNS software is not running on either server. Doublecheck to make sure that BIND (or whatever progam is installed) is actually running. If you have started it, check the logs and make sure it didn't die after it start up.