bearclaws75
asked on
New subdomains not ping-ing
I created a new domain (newdomain.com) and several subdomains. I pointed each record to the server IP. I can successfully ping the "www" domain but I can't ping the subdomains.
When I ping "www.newdomain.com", I get this:
PING www.newdomain.com (12.34.199.123) 56(84) bytes of data.
64 bytes from servername (12.34.199.123): icmp_seq=1 ttl=47 time=41.0 ms
64 bytes from servername (12.34.199.123): icmp_seq=2 ttl=47 time=40.8 ms
64 bytes from servername (12.34.199.123): icmp_seq=3 ttl=47 time=40.9 ms
....but when I ping "test.newdomain.com, I get this first line:
PING test.newdomain.com (12.34.199.123) 56(84) bytes of data.
...and then nothing happens.
Any ideas?
My server info:
* Fedora release 7 (Moonshine)
* Server version: Apache/2.2.6 (Unix)
When I ping "www.newdomain.com", I get this:
PING www.newdomain.com (12.34.199.123) 56(84) bytes of data.
64 bytes from servername (12.34.199.123): icmp_seq=1 ttl=47 time=41.0 ms
64 bytes from servername (12.34.199.123): icmp_seq=2 ttl=47 time=40.8 ms
64 bytes from servername (12.34.199.123): icmp_seq=3 ttl=47 time=40.9 ms
....but when I ping "test.newdomain.com, I get this first line:
PING test.newdomain.com (12.34.199.123) 56(84) bytes of data.
...and then nothing happens.
Any ideas?
My server info:
* Fedora release 7 (Moonshine)
* Server version: Apache/2.2.6 (Unix)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
pretty sure you need to update the routing table on both domains (add route statements)
ASKER
Yes - i created dns records for the "www" and the subdomains:
www A 12.34.199.123
test A 12.34.199.123
I am using Direct Admin to manage the DNS records.
www A 12.34.199.123
test A 12.34.199.123
I am using Direct Admin to manage the DNS records.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I just checked Godaddy (where the domain was registered by the client) and the nameservers did not look correct.
I updated these and will check again in a few hours. We manage a number of domains via Direct Admin and haven't experienced this issue before, so I'm hoping that was the problem.
I'll provide an update later tonight...
Thanks for you input so far!
I updated these and will check again in a few hours. We manage a number of domains via Direct Admin and haven't experienced this issue before, so I'm hoping that was the problem.
I'll provide an update later tonight...
Thanks for you input so far!
Let us know how you go.
ASKER
False alarm...this turned out to be an issue with the nameservers. They were configured incorrectly at the domain registrar. All sub-domains are now working.
I'll distribute points evenly as everybody was helpful (and provided valid troubleshooting).
Cheers.
I'll distribute points evenly as everybody was helpful (and provided valid troubleshooting).
Cheers.
ASKER