Serving up two domains

[Jason Hellenthal]

Hey thanks for replying Doug.

Sorry for the top post.. iPhone.

Anyway yes these are private or internal zones.

Software is more so the root cause but attempts to resolve to hostname.tld from a device that's managed from domain.tld where you'd expect to see it asking for hostname.domain.tld instead.

Seems all apple related traffic and services where I've seen an answer for this once before but don't recall it.

I see the requests come by through a monitor port of the network with wireshark where it asks for the above and never attempts to resolve another internal FQDN.

TMK it's multicast group traffic to 224.0.0/24 from apple devices or similar that I'm just uninterested in filling those out correctly ATM and would rather just point the back to the actuall IP of the devices it's asking for until I fill in the gap at a later time.

The search list the DHCP clients get are that of the internal domain itself.
Like: search domain.tld


-- 
 Jason Hellenthal
 Inbox: jhellenthal at DataIX.net
 Voice: +1 (616) 953-0176
 JJH48-ARIN


On Jun 12, 2013, at 0:24, Doug Barton <dougb at dougbarton.us> wrote:

> Jason,
> 
> What you're saying here doesn't make sense, so some more details are needed.
> 
> On 06/11/2013 08:54 PM, Jason Hellenthal wrote:
>> 
>> I have a domain or two that I'm serving up and have traffic from some
>> mobile devices and a few pieces of software that also try to resolve to
>> the hostname.tld instead of what normally would be expected to be
>> hostname.domain.tld.
> 
> Is what you wrote above what you meant to write? If so that's very surprising. Can you give some more details? Are these private zones, or are you seeing this traffic from the Internet? Is there a search list involved? If so, and tld is listed before domain.tld that would make sense, and it should be fixed there.
> 
>> Not really concerned with why but rather would just like to allow them
>> to resolve to the same address as the .domain.tld.
> 
> If you really are seeing traffic trying to resolve hostname.tld, you probably need to fix the root problem rather than trying to support the bad behavior.
> 
> hth,
> 
> Doug
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20130612/f7ac2f5f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2529 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20130612/f7ac2f5f/attachment-0001.bin>