Forward zone problem

OK.

But this is DNS working between Wireless service providers.

Each provider (Verizon, Cingular, Voicestream, etc) maintain DNS entries for the APNs that they offer for their customers.

As customers roam into different coverage areas, their queries for APNs are received by other carrier's DNS servers, and the carriers forward these queries back to the correct DNS servers of the "home" DNS for these roamers.

If I am Verizon, I maintain APNs for my zone, which is (say) mnc340.mcc310.gprs . Inside that zone are A records for my wap server, mms server, etc.

Your Roaming Partner agreements specifies which forward zone and associated IPs you should use for the roamers passing into your area.

And I still don't understand how the forward zone:

zone "mnc410.mcc310.gprs" {
type forward;
forwarders { ips for the Cingular DNS server;}; };
works fine.

Yet, the new one I created for mnc610.mcc310.gprs is not working.

I have to look into every local zone file, and see if somehow this DNS servers thinks it is somehow authoritive for this domain someplace.

  Latest articles

Configuring bind not to use unprivileged ports?

Multi sub-domain -> same ip