• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 604
  • Last Modified:

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)

0
bearclaws75
Asked:
bearclaws75
  • 4
  • 2
  • 2
  • +2
4 Solutions
 
pschakravarthiCommented:
In subdomain configure default  to your server IP
0
 
bearclaws75Author Commented:
Can you clarify what you mean?
0
 
savoneCommented:
Did you create dns records for your subdomain?
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
ggefterCommented:
pretty sure you need to update the routing table on both domains (add route statements)
0
 
bearclaws75Author Commented:
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.
0
 
ggefterCommented:
0
 
CrunchedCommented:
It sounds like you have done everything correctly, so maybe Direct Admin is causing your issues? Have you tried creating/checking the DNS records manually?

Is the client you are trying to ping from using the correct DNS server(s)? It isn't using a host file is it?
0
 
bearclaws75Author Commented:
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!
0
 
CrunchedCommented:
Let us know how you go.
0
 
bearclaws75Author Commented:
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.
0

Featured Post

SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

  • 4
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now