<![CDATA[1.2.3 and DNS]]>So I needed to run some test and be able to setup an override forward to an internal server on my flat network (on the same subnet).  No domains.

For a while, it didn't appear that things were working.  My quick test was to try and PING the hostname.domain.

Just by pure accident, I started one of these PINGs and then went off working on something else.  I noticed that it started replying…when I really hadn't changed anything.
After a few tests, here's what I'm seeing.

If I just PING hostname, instant response.
If I PING hostname.domain, it takes right at 15 sec. before I start seeing replies.

Is there any reason I should expect this behavior to be normal?

]]>https://forum.netgate.com/topic/36170/1-2-3-and-dnsRSS for NodeWed, 11 Mar 2026 23:05:57 GMTWed, 10 Aug 2011 02:34:30 GMT60<![CDATA[Reply to 1.2.3 and DNS on Wed, 17 Aug 2011 17:17:37 GMT]]>@ck42:

If I just PING hostname, instant response.
If I PING hostname.domain, it takes right at 15 sec. before I start seeing replies.

That sounds like the look-up for hostname.domain is being routed to a DNS server, that cannot be reached, and so is timing out.

Cheers.

]]>https://forum.netgate.com/post/292069https://forum.netgate.com/post/292069Wed, 17 Aug 2011 17:17:37 GMT