Time for Sub-Domain to go Live?

So, you're going to have two websites with PUBLIC domains which resolve to PUBLIC IP's yet you expect people who may be able to help you go thru sometype of weird Captain Crunch Decoder Ring exercise to decrypt what little info you actually provided.

Good luck with that.

@vonskippy:

So, you're going to have two websites with PUBLIC domains which resolve to PUBLIC IP's yet you expect people who may be able to help you go thru sometype of weird Captain Crunch Decoder Ring exercise to decrypt what little info you actually provided.

Good luck with that.

Nice. Friendly guy.

main domain is: www.timeclockmts-online.com (173.230.147.22)

second IP is: 97.107.133.228 which I am trying to get to resolve to leonard.timeclockmts-online.com

Works for me

% getent hosts leonard.timeclockmts-online.com
97.107.133.228  leonard.timeclockmts-online.com

(See how easy it was for me to check, once you'd provided real information - vonskippy is correct; if you don't give us enough information then we can't help!)

@sweh:

Works for me

% getent hosts leonard.timeclockmts-online.com
97.107.133.228  leonard.timeclockmts-online.com

(See how easy it was for me to check, once you'd provided real information - vonskippy is correct; if you don't give us enough information then we can't help!)

Oh I agree, but "if you don't give us enough information then we can't help" is a much nicer way of putting things that the tripe above.

Thanks for your help by the way :) Is there a reason why my other sub-domains (set up several weeks ago) would be returning correctly via the host command and this new one isn't? Is this just a time issue?

Check your cache.

It's possible the DNS server you're using has cached the NXDOMAIN and so isn't looking it up.

If you ask a different DNS server you may see it works

eg

% host leonard.timeclockmts-online.com 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:

leonard.timeclockmts-online.com has address 97.107.133.228

Great, that's it then. Thanks very much for help :)

@markn:

is a much nicer way of putting things that the tripe above.
Ahhhh, you wanted technical help AND some warm milk and cookies.

It helps to be more specific.

@vonskippy:

@markn:

is a much nicer way of putting things that the tripe above.
Ahhhh, you wanted technical help AND some warm milk and cookies.

It helps to be more specific.

Cookies would be nice, thanks for asking :) Thanks to all for help.

Your negative caching TTL (the last value in the SOA record) is set to 86400, so your resolver could cache the result up to a day. (Or longer, if it's a jerk and ignores TTLs, but we'll ignore that issue.) Just FYI, the recommended value for that setting is usually just a couple hours.