Has anybody heard of a IP not routing correctly?

070707

New member
Mar 13, 2008
1,827
21
0
Ma's Basement
I wake up 5 days ago... website is not down, but forwards to a domain holder type landing page. wtf.

Contact support... They said the IP address "is not routing correctly" and we changed my IP for the website. All becomes well again.

I wake up this morning... same exact issue, and same exact response... change the IP, and nothing happens. Stuck on this fucking holder page and support thinks I am smoking crack saying that IP's don't just route incorrectly.... when that is what THEY told me.

What the fuck could have happened?
 


Could be a number of things, such as DNS cache of certain providers not being flushed in a timely manner, I see this a lot mainly with Internet Provider's cache, even though they're all supposed to flush the cache at the record's TTL (Time-To-Live).

How is your domain setup? Are you using a nameserver, or their internal DNS, which registrar?

Once had a guy who somehow had two different sets of nameservers in his whois.
 
Go thru some proxies and see if it looks different; if it does, maybe add another nameserver. If it always looks like that no matter what proxy you go thru and they tell you "IP not routing correctly", ask them to escalate your ticket because you need someone who knows about BIND and whatever script they use to manage it.
 
Could be a number of things, such as DNS cache of certain providers not being flushed in a timely manner, I see this a lot mainly with Internet Provider's cache, even though they're all supposed to flush the cache at the record's TTL (Time-To-Live).

How is your domain setup? Are you using a nameserver, or their internal DNS, which registrar?

Once had a guy who somehow had two different sets of nameservers in his whois.

Custom nameserver. Whois shows the correct nameservers. These... "ping your website" sites show the correct IP, but when I ping from the cmd function on windows... it shows some random IP.
 
Go thru some proxies and see if it looks different; if it does, maybe add another nameserver. If it always looks like that no matter what proxy you go thru and they tell you "IP not routing correctly", ask them to escalate your ticket because you need someone who knows about BIND and whatever script they use to manage it.

Some show the site, some don't. My phone shows it... my house, my school, everything doesn't... even at the support at the hosts can't.
 
FWIW, this is a BS excuse I have gotten from hosting providers before. Not saying it definitely is in your case, but it could be.
 
Just for future reference, if you have access to a *nix shell (dreamhost, vps, any decent host offers ssh access..), the "dig" command is great for interrogating name servers.

Some examples...
Code:
bigbrother ~:# dig @4.2.2.3 digg.com A

; <<>> DiG 9.5.1-P3 <<>> @4.2.2.3 digg.com A
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8886
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;digg.com.			IN	A

;; ANSWER SECTION:
digg.com.		3458	IN	A	64.191.203.30

;; Query time: 45 msec
;; SERVER: 4.2.2.3#53(4.2.2.3)
;; WHEN: Mon Jan 18 14:07:59 2010
;; MSG SIZE  rcvd: 42

bigbrother ~:# dig @8.8.4.4 digg.com MX

; <<>> DiG 9.5.1-P3 <<>> @8.8.4.4 digg.com MX
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27890
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;digg.com.			IN	MX

;; ANSWER SECTION:
digg.com.		3391	IN	MX	0 mail.digg.com.
digg.com.		3391	IN	MX	100 diggstage01.digg.com.

;; Query time: 83 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Mon Jan 18 14:08:14 2010
;; MSG SIZE  rcvd: 75

bigbrother ~:# dig @8.8.8.8 digg.com NS

; <<>> DiG 9.5.1-P3 <<>> @8.8.8.8 digg.com NS
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15105
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;digg.com.			IN	NS

;; ANSWER SECTION:
digg.com.		1863	IN	NS	UDNS2.ULTRADNS.NET.
digg.com.		1863	IN	NS	UDNS1.ULTRADNS.NET.

;; Query time: 67 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Jan 18 14:08:22 2010
;; MSG SIZE  rcvd: 78

bigbrother ~:# dig @UDNS2.ULTRADNS.NET digg.com A

; <<>> DiG 9.5.1-P3 <<>> @UDNS2.ULTRADNS.NET digg.com A
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24511
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;digg.com.			IN	A

;; ANSWER SECTION:
digg.com.		3600	IN	A	64.191.203.30

;; AUTHORITY SECTION:
digg.com.		3600	IN	NS	UDNS2.ULTRADNS.NET.
digg.com.		3600	IN	NS	UDNS1.ULTRADNS.NET.

;; Query time: 91 msec
;; SERVER: 204.74.101.1#53(204.74.101.1)
;; WHEN: Mon Jan 18 14:08:32 2010
;; MSG SIZE  rcvd: 94

bigbrother ~:#

Or just use intodns :D Anyway, glad everything eventually worked out.