Odd DNS Behavior

[WCrooks]

Several days ago I changed my dns to a different server -- I realize it can take up to a week for dns to properly resolve -- however, the issues I'm having don't seem to lead me to believe it's simply a dns issue.

Symptoms:

-Some sites function all the time
-Some sites function one day, then stop working
-Some sites do not work at all for me, but work for users in Saskatchewan and The Netherlands, but not for users as close as an hour away from me

Altera results are as follows for non-working domains:

01/29/2006 08:18:35 Las Vegas USA OK 27.1 2.27 97.59
01/29/2006 08:18:36 Atlanta USA OK 27.1 2.47 89.78
01/29/2006 08:18:36 Orlando USA OK 27.1 2.77 80.17
01/29/2006 08:18:35 Chicago USA OK 27.1 2.29 96.86
01/29/2006 08:18:38 London UK OK 27.1 4.29 51.66
01/29/2006 08:18:35 Oklahoma City USA Error N/A 1.58 N/A


01/29/2006 08:20:02 Oklahoma City USA Error N/A 1.46 N/A
01/29/2006 08:20:01 Chicago USA OK 3.9 0.64 50.19
01/29/2006 08:20:01 Atlanta USA OK 3.9 0.80 40.17
01/29/2006 08:20:06 Frankfurt GERMANY OK 3.9 5.15 6.22
01/29/2006 08:20:01 Orlando USA OK 3.9 0.99 32.41
01/29/2006 08:20:01 Las Vegas USA OK 3.9 0.77 41.37
01/29/2006 08:20:04 Hong Kong CHINA OK 3.9 3.00 10.69
01/29/2006 08:20:02 London UK OK 3.9 1.51 21.18

01/29/2006 08:21:00 Orlando USA OK 13.8 1.49 75.78
01/29/2006 08:21:00 Chicago USA OK 13.8 1.45 77.98
01/29/2006 08:21:00 Atlanta USA OK 13.8 1.46 77.58
01/29/2006 08:21:00 Oklahoma City USA Error N/A 1.52 N/A
01/29/2006 08:21:03 Hong Kong CHINA OK 13.8 4.35 25.95
01/29/2006 08:21:00 Las Vegas USA OK 13.8 1.49 75.56
01/29/2006 08:21:00 London UK OK 13.8 1.80 62.64

01/29/2006 08:21:48 Frankfurt GERMANY OK 1.2 5.00 1.96
01/29/2006 08:21:43 Atlanta USA OK 1.2 0.77 12.65
01/29/2006 08:21:44 Orlando USA OK 1.2 0.96 10.22
01/29/2006 08:21:46 Hong Kong CHINA OK 1.2 2.99 3.27
01/29/2006 08:21:43 Chicago USA OK 1.2 0.69 14.28
01/29/2006 08:21:43 Las Vegas USA OK 1.2 0.77 12.67
01/29/2006 08:21:44 London UK OK 1.2 1.51 6.47
01/29/2006 08:21:44 Oklahoma City USA Error N/A 1.45 N/A

01/29/2006 08:23:45 Frankfurt GERMANY OK 9.5 4.06 19.15
01/29/2006 08:23:42 Las Vegas USA OK 9.5 0.94 82.32
01/29/2006 08:23:42 Atlanta USA OK 9.5 0.89 87.81
01/29/2006 08:23:42 Orlando USA OK 9.5 1.08 72.45
01/29/2006 08:23:41 Chicago USA OK 9.5 0.72 107.34
01/29/2006 08:23:45 Hong Kong CHINA OK 9.5 3.48 22.41
01/29/2006 08:23:42 Oklahoma City USA Error N/A 1.48 N/A
01/29/2006 08:23:42 London UK OK 9.5 1.74 44.68

working domain:

01/29/2006 09:45:56 Orlando USA OK 3.7 0.41 74.06
01/29/2006 09:45:57 Frankfurt GERMANY OK 3.7 1.13 26.53
01/29/2006 09:45:56 Atlanta USA OK 3.7 0.30 101.77
01/29/2006 09:45:58 Hong Kong CHINA OK 3.7 1.74 17.32
01/29/2006 09:45:56 Las Vegas USA OK 3.7 0.55 54.98
01/29/2006 09:45:56 Chicago USA OK 3.7 0.24 123.98
01/29/2006 09:45:56 Oklahoma City USA OK 3.7 0.35 87.07
01/29/2006 09:45:56 London UK OK 3.7 0.71 42.64


clearly Oklahoma doesn't work for the ones that don't work -- but that doesn't explain why the ones that did work all of a sudden "stopped" working -- in fact...at least one of those non-functioning domains had a perfect alerta result yesterday.

The error(s) returned from altera is as follows:

TIMEOUT 30
ERR Unable to resolve name

LAST_EXEC_TIME = 0.676115036011
LAST_MSG = Unable to resolve name
LAST_TIMESTAMP = 1138549548.01
TRACEABLE = N
LAST_COMMAND = DNS
LAST_PROTO_MSG = Name or service not known
TOTAL_RUNTIME = 0.676362037659
LAST_CODE = 3
LAST_PROTO_CODE = -2


TIMEOUT 30
DNS www.domain.com 67.18.208.30 0.0869648456573
TCP 80 0.0215780735016
ERR Connection to HTTP service failed

LAST_REQUEST = http://www.domain.com/
STAT_TIME_TO_LAST_BYTE = 0
LAST_MSG = Connection to HTTP service failed
LAST_EXEC_TIME = 1.47252011299
LAST_TIMESTAMP = 1138549589.93
LAST_PROTO_CODE = ERR
LAST_IP = 67.18.208.30
LAST_CODE = 3
STAT_TOTAL_BYTES_WRITTEN = 0
LAST_COMMAND = HTTP
LAST_PROTO_MSG = Unrecognized HTTP error
LAST_HOST = www.domain.com
STAT_TOTAL_BYTES_READ = 0
TOTAL_RUNTIME = 1.58168721199
STAT_TIME_TO_FIRST_BYTE = 0
TRACEABLE = Y
STAT_CONNECT_TIME = 0
STAT_WRITE_TIME = 0


I'm at my wits end and I've tried everything I could think of -- so if anyone has any suggestions they would be extremely appreciated.

Thanks.

[sawbuck]

Assume you changed the resolv.conf to match new name servers?

Care to post a domain that someone can check?

[WCrooks]

Yeah -- resolv.conf is configured correctly, nameservers are setup, a records are added.

Here is a dns report on one of the domains:

http://dnsreport.com/tools/dnsreport...ianhosting.com

primary nameserver: ns1.avianhosting.com
secondary nameserver: ns2.avianhosting.com
domain name: avianhosting.com

Thank You for the quick response!

[sawbuck]

Don't see anything out of the ordinary except the traceroute on 67.18.208.30 and .31 goes to tailormadeservers.com.

Assume you are on a reseller account?

[WCrooks]

Nope. It's a dedicated from TMS.

[sawbuck]

And you have control of tailormadeservers.com?

[WCrooks]

Actually no -- the two ips are among the ranges we were assigned with the server... -- so I'm not sure why they're tracerouting to the dc domain instead..

[sawbuck]

Sounds then like a mis-config at the DC.

[easyhoster1]

Time to get on the phone with your NOC and ask why tailormadeservers.com
has a zone with your IP. Looks like a screw up on their part for giving out IP's
that already have been issued to someone else. Or a mis-config cluster?

# dig AVIANHOSTING.COM

; <<>> DiG 9.3.0 <<>> AVIANHOSTING.COM
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13528
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;AVIANHOSTING.COM. IN A

;; ANSWER SECTION:
AVIANHOSTING.COM. 14400 IN A 67.18.208.30

;; Query time: 157 msec
;; SERVER: 207.99.0.1#53(207.99.0.1)
;; WHEN: Sun Jan 29 13:40:54 2006
;; MSG SIZE rcvd:

traceroute AVIANHOSTING.COM
traceroute to AVIANHOSTING.COM (67.18.208.30), 64 hops max, 40 byte packets

2 0.so-7-3-0.gbr1.mmu.nac.net (209.123.11.145) 1.106 ms 1.041 ms 0.982 ms
3 0.so-3-0-0.gbr1.tl9.nac.net (209.123.11.54) 46.213 ms 3.708 ms 3.605 ms
4 ge-3-3-0.cr1.lga3.us.above.net (64.21.34.174) 2.858 ms 2.835 ms 2.856 ms
5 so-4-0-0.mpr2.lga1.us.above.net (64.125.30.21) 3.234 ms 24.304 ms 25.365 ms
6 so-4-0-0.cr2.lga1.us.above.net (64.125.27.153) 3.336 ms 3.210 ms 3.229 ms
7 so-1-0-0.mpr2.iad1.us.above.net (64.125.28.65) 8.481 ms 8.423 ms 8.352 ms
8 so-1-0-0.cr2.dca2.us.above.net (64.125.28.129) 9.980 ms 8.799 ms 8.730 ms
9 so-2-2-0.cr2.dfw2.us.above.net (64.125.29.9) 36.714 ms 36.661 ms 36.587 ms
10 216.200.6.237.theplanet.com (216.200.6.237) 43.211 ms 43.330 ms 43.205 ms
11 vl32.dsr01.dllstx3.theplanet.com (70.85.127.61) 43.206 ms vl31.dsr01.dllstx3.theplanet.com (70.85.127.29) 42.973 ms vl31.dsr02.dllstx3.theplanet.com (70.85.127.30) 43.152 ms
12 vl21.dsr01.dllstx2.theplanet.com (70.85.127.67) 43.151 ms vl22.dsr02.dllstx2.theplanet.com (70.85.127.76) 43.533 ms 43.156 ms
13 vl2.car06.dllstx2.theplanet.com (12.96.160.52) 43.709 ms 43.539 ms 43.457 ms
14 70.69-41-232.reverse.theplanet.com (69.41.232.70) 43.959 ms 44.062 ms 44.204 ms
15 67.18.208.30.tailormadeservers.com (67.18.208.30) 43.331 ms 43.350 ms 43.455 ms

tailormadeservers.com should be answering on
216.66.18.30

; <<>> DiG 9.3.0 <<>> tailormadeservers.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64710
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

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

;; ANSWER SECTION:
tailormadeservers.com. 86378 IN A 216.66.18.30

;; AUTHORITY SECTION:
tailormadeservers.com. 86378 IN NS ns2.tailoredservers.com.
tailormadeservers.com. 86378 IN NS ns.tailoredservers.com.

;; Query time: 216 msec

[WCrooks]

Thanks guys. It's much appreciated. I'll let you all know what happens.

[WCrooks]

-tech's name removed for privacy-
29-1-2006-1:27

What do you mean by 'zones'? Do you mean the reverse DNS entries? You can update those in the reverse DNS area in the helpdesk.

-- don't tell me all this time the problem was because I missed a page in my dc's control panel?

67.18.208.30.tailormadeservers.com
67.18.208.31.tailormadeservers.com

these are the "zones" you guys were referring to, correct?If so...I can change those.


And if so..furthermore..I feel like an idiot.

[sawbuck]

Those rDNS entries should be changed to avianhosting.com.

Run the trace route after making the change to confirm whether avianhosting.com is pointed to 67.18.208.30. If not then post that trace route to the help desk at the DC.

[WCrooks]

Yep. That worked.

I feel like such an idiot -- after all of this it comes down to rdns entries. That domain worked immediately afterward..but the others I imagine still need time I would assume -- I would gather if they don't work by 4:30 tommorrow or such that I may have another problem (it's 4:30 here now approximately). I added the rdns for my nameservers (ns1.avianhosting.com the first ip, ns2 the second) using the cp. Now that I think of it -- I shouldeve known that >.<

Thanks Again both of you. Your help is extremely appreciated.

[sawbuck]

Are you seeing a different trace route than this?

traceroute avianhosting.com
traceroute to avianhosting.com (67.18.208.30), 30 hops max, 38 byte packets
1 192.168.0.19 (192.168.0.19) 0.174 ms 0.195 ms 0.100 ms
2 ge3-1.cr02.vna01.pccwbtn.net (63.218.97.157) 0.528 ms 0.757 ms 0.491 ms
3 ge3-3.br01.dal01.pccwbtn.net (63.218.22.62) 38.460 ms 38.202 ms 39.724 ms
4 theplanet.ge2-4.br01.dal01.pccwbtn.net (63.218.23.26) 37.505 ms 37.182 ms 37.410 ms
5 vl32.dsr02.dllstx3.theplanet.com (70.85.127.62) 36.805 ms 37.639 ms 37.931 ms
6 vl22.dsr02.dllstx2.theplanet.com (70.85.127.76) 37.681 ms 37.427 ms 39.127 ms
7 vl1.car06.dllstx2.theplanet.com (12.96.160.20) 37.599 ms 37.747 ms 37.496 ms
8 70.69-41-232.reverse.theplanet.com (69.41.232.70) 38.003 ms 38.025 ms 37.890 ms
9 67.18.208.30.tailormadeservers.com (67.18.208.30) 37.552 ms 37.997 ms 37.812 ms

[WCrooks]

Tracing route to avianhosting.com [67.18.208.30]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  . [192.168.2.1]
  2    15 ms    15 ms    14 ms  hlfxns0145w-loop0.aliant.net [142.166.182.89]
  3    13 ms    13 ms    13 ms  alns-dr01-ge-7-0.aliant.net [142.166.182.195]
  4    24 ms    43 ms    26 ms  rtp629049rts [64.230.203.33]
  5    13 ms    13 ms    12 ms  rtp629021rts [64.230.166.53]
  6    30 ms    30 ms    31 ms  rtp629032rts [64.230.166.34]
  7    38 ms    39 ms    38 ms  rtp627407rts [64.230.204.134]
  8    75 ms    41 ms    38 ms  bx2-newyork83-pos3-0.in.bellnexxia.net [206.108.
103.194]
  9    39 ms    39 ms    39 ms  so-4-3-0.pr2.lga1.us.above.net [64.125.12.33]
 10    40 ms    40 ms    40 ms  so-5-0-0.cr2.lga1.us.above.net [64.125.27.138]
 11    44 ms    44 ms    60 ms  so-1-0-0.mpr2.iad1.us.above.net [64.125.28.65]
 12    45 ms    45 ms    45 ms  so-1-0-0.cr2.dca2.us.above.net [64.125.28.129]
 13    71 ms    71 ms    72 ms  so-2-2-0.cr2.dfw2.us.above.net [64.125.29.9]
 14    74 ms    74 ms    75 ms  216.200.6.237.theplanet.com [216.200.6.237]
 15   134 ms   223 ms   215 ms  vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]

 16    91 ms    91 ms    90 ms  vl22.dsr02.dllstx2.theplanet.com [70.85.127.76]

 17    75 ms    79 ms    74 ms  vl2.car06.dllstx2.theplanet.com [12.96.160.52]
 18    75 ms    76 ms    74 ms  70.69-41-232.reverse.theplanet.com [69.41.232.70
]
 19    76 ms    74 ms    75 ms  [domain on server -- I should fix that as well] [67.18.208.30]

Trace complete.

For the record, theres still about 20 domains that don't load server wise...but I'm guessing those will work tommorrow.

btw, I apologise for the late response -- the power was out for the last 4 hours here.