whm and dns issues

[intel352]

sup guys, i recently moved from a plesk-based server, to a WHM/cpanel-based server...

i enjoy the power of cpanel/whm so far, but i've run into one bad issue.

when i moved all of the sites that i hosted to the new server, i created 3 main accounts:

• 1 acct for myself, where i've been installing all my subdomains and addon domains, assigned to a dedicated ip
• 2 other accounts for 2 friends who both run a few small public or test sites

the domains for all 3 accounts use the same nameservers to resolve

i updated the nameserver ips at godaddy.com, and now my own websites are correctly pointing to the new ip, and correctly loading


when i attempt to visit one of my buddies websites, the page will not load. i do a ping, it fails (even tho it lists the ip before it starts pinging, and it's the correct ip, ***.***.***.170)

i run a tracert, it starts as if it's final goal is ***.***.***.170, but it ends up at what appears to be another ip in the host's network, where the tracert dies

is there any possible idea what i may have setup up incorrectly when i assigned these domains? i checked httpd.conf, it shows the correct ips for each domain (defaults to ***.***.***.170), and i see no obviously incorrect settings, so i have no clue what the problem is

oh, and the dns zone info appears correct as well...

if anyone can help, please do so... thanks

[intel352]

i'm posting this info for the benefit of the Cpanel support team, but if anyone else can help, please do so:

csmapcentral image 1

csmapcentral image 2 (rest of the dns entries)

non-working domain, whosyourdaddycool.com <<<


the csmapcentral domains and subdomains all work properly, resolve properly, etc..

the daddycool domain does not work properly

here's a traceroute for csmapcentral:

C:\Documents and Settings\Jon>tracert csmapcentral.com

Tracing route to csmapcentral.com [66.79.166.179]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 7 ms 8 ms 10.32.144.1
3 9 ms 8 ms 9 ms fas2-7.gnbonckrn-rtr1.triad.rr.com [24.28.228.20
9]
4 9 ms 9 ms 10 ms srp10-0.gnboncsg-rtr1.triad.rr.com [24.28.224.22
5]
5 9 ms 9 ms 10 ms srp1-0.gnboncsg-rtr4.triad.rr.com [24.28.226.195
]
6 13 ms 12 ms 12 ms son0-0-2.chrlncsa-rtr6.carolina.rr.com [24.93.64
.41]
7 13 ms 16 ms 12 ms pop1-cha-P4-0.atdn.net [66.185.132.45]
8 12 ms 12 ms 11 ms bb1-cha-P0-0.atdn.net [66.185.138.64]
9 19 ms 16 ms 18 ms bb1-atm-P6-0.atdn.net [66.185.152.182]
10 18 ms 17 ms 17 ms pop1-atm-P4-0.atdn.net [66.185.150.1]
11 18 ms 17 ms 20 ms pos8-0.er1.atl4.us.above.net [209.249.119.241]
12 40 ms 39 ms 40 ms so-5-0-0.cr2.dfw2.us.above.net [216.200.127.226]

13 39 ms 38 ms 37 ms so-0-0-0.cr1.dfw2.us.above.net [216.200.127.209]

14 88 ms 88 ms 88 ms so-4-1-0.mpr4.sjc2.us.above.net [64.125.29.57]
15 88 ms 85 ms 83 ms so-0-0-0.er10a.sjc2.us.above.net [64.125.30.94]

16 87 ms 89 ms 87 ms 209.66.79.101.available.assertivenetworks.net [2
09.66.79.101]
17 85 ms 85 ms 85 ms 66-154-102-5.assertivenetworks.net [66.154.102.5
]
18 85 ms 86 ms 84 ms 66.79.166.179

Trace complete.

now, here's a traceroute for daddycool's site... you can see how it breaks down towards the end, hitting the wrong computers...

C:\Documents and Settings\Jon>tracert whosyourdaddycool.com

Tracing route to whosyourdaddycool.com [66.79.160.170]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 8 ms 10.32.144.1
3 9 ms 9 ms 8 ms fas2-7.gnbonckrn-rtr1.triad.rr.com [24.28.228.20
9]
4 11 ms 8 ms 10 ms srp10-0.gnboncsg-rtr1.triad.rr.com [24.28.224.22
5]
5 9 ms 11 ms 10 ms srp1-0.gnboncsg-rtr4.triad.rr.com [24.28.226.195
]
6 12 ms 11 ms 12 ms son0-0-2.chrlncsa-rtr6.carolina.rr.com [24.93.64
.41]
7 12 ms 12 ms 13 ms pop1-cha-P4-0.atdn.net [66.185.132.45]
8 13 ms 11 ms 12 ms bb1-cha-P2-0.atdn.net [66.185.132.40]
9 20 ms 18 ms 18 ms bb1-atm-P6-0.atdn.net [66.185.152.182]
10 17 ms 17 ms 17 ms pop1-atm-P0-0.atdn.net [66.185.147.193]
11 17 ms 20 ms 17 ms pos8-0.er1.atl4.us.above.net [209.249.119.241]
12 38 ms 38 ms 40 ms so-5-0-0.cr2.dfw2.us.above.net [216.200.127.226]

13 38 ms 37 ms 38 ms so-0-0-0.cr1.dfw2.us.above.net [216.200.127.209]

14 88 ms 89 ms 88 ms so-4-1-0.mpr4.sjc2.us.above.net [64.125.29.57]
15 85 ms 84 ms 84 ms so-0-0-0.er10a.sjc2.us.above.net [64.125.30.94]

16 91 ms 88 ms 91 ms 209.66.79.101.available.assertivenetworks.net [2
09.66.79.101]
17 66-154-102-5.assertivenetworks.net [66.154.102.5] reports: Destination hos
t unreachable.

Trace complete.

both nameservers (ns.csmapcentral.com and ns2.csmapcentral.com) have been registered for the better part of a year... i updated the ip addresses for the 2 nameservers at godaddy.com, and the new nameserver information has already propagated for the most part

daddycool's site has been registered to both nameservers for several months now, there's been no change (and you can see in the traceroute that the trace INTENDS to hit 66.79.166.170, but doesn't, it had to get that dns info somewhere..)


please note, these dns zones were created by WHM when i added the domains/accts. the csmapcentral domains work fine without the * entry, but i added the * entry to the daddycool domain as you suggested (i was talking via pm to another server admin on another forum, regarding a suggestion he made)


please tell me what you think... seems weird to me that the daddycool domain (as well as any other domains on the box that aren't allocated a dedicated ip address) all try to hit that dead/unresponsive server

_________________________________________________

btw, i have the following nameservers:
ns.csmapcentral.com : 66.79.166.170
ns2.csmapcentral.com : 66.79.166.171
ns.nukebbmods.net : 66.79.166.172
ns.nukebbmods.net : 66.79.166.173

66.79.166.174, .175, .176, .177, .178 are all free, and .179 is dedicated to the csmapcentral.com account