Resolving a specific domain cause problems
a.r.kuiters at kpn.com
a.r.kuiters at kpn.com
Mon Jun 27 13:06:53 UTC 2005
Ok so it's not a gTLD but it should act as a gTLD isn't it?
This is a part of our file
$TTL 86400
gprs. IN SOA ns1.mnc008.mcc204 root.ns1.mnc008.mcc204 (
2005062303 ; serial
3600 ; refresh every 60 min
900 ; retry every 15 min
604800 ; expire after a week
86400 ; minimum TTL 1 day
)
IN NS ns1.mnc008.mcc204.gprs.
IN NS ns2.mnc008.mcc204.gprs.
mnc002.mcc238 IN NS ns1.mnc002.mcc238
IN NS ns2.mnc002.mcc238
mnc001.mcc206 IN NS ns1.mnc001.mcc206
IN NS ns2.mnc001.mcc206
mnc003.mcc262 IN NS ns1.mnc003.mcc262
IN NS ns2.mnc003.mcc262
mnc002.mcc228 IN NS ns1.mnc002.mcc228
IN NS ns2.mnc002.mcc228
mnc341.mcc722 IN NS ns1.mnc341.mcc722
IN NS ns2.mnc341.mcc722
ns1.mnc002.mcc238 IN A 212.88.72.11
ns2.mnc002.mcc238 IN A 212.88.72.12
ns1.mnc001.mcc206 IN A 213.181.60.1
ns2.mnc001.mcc206 IN A 213.181.60.2
ns1.mnc003.mcc262 IN A 212.23.99.33
ns2.mnc003.mcc262 IN A 212.23.99.96
ns1.mnc002.mcc228 IN A 212.161.168.149
ns2.mnc002.mcc228 IN A 212.161.168.150
ns3.mnc002.mcc228 IN A 212.161.168.174
ns1.mnc341.mcc722 IN A 200.43.139.95
ns2.mnc341.mcc722 IN A 200.43.139.96
And a part of named.conf
# more named.conf
// generated by named-bootconf.pl
options {
directory "/etc/named.data"; // running directory for named
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
controls {
inet 127.0.0.1 allow {localhost;} keys {rndckey;};
};
key "rndckey" {
algorithm hmac-md5;
secret "abcdefghijklmnopqrstuvwxyz";
};
//
// type domain source file
//
zone "gprs" {
type master;
file "db.gprs";
};
Could the first gprs. in the specific domain causes the problem?
-----Oorspronkelijk bericht-----
Van: Brad Knowles [mailto:brad at stop.mail-abuse.org]
Verzonden: maandag 27 juni 2005 14:55
Aan: Kuiters, A.R. (OMN)
CC: brad at stop.mail-abuse.org; Ammerlaan, N.J. (OMN); Goudzwaard, R.
(OMN); bind-users at isc.org
Onderwerp: RE: Resolving a specific domain cause problems
At 2:50 PM +0200 2005-06-27, a.r.kuiters at kpn.com wrote:
> The domain is specific to mobile packet switched networks:
> gprs.personal.com.mnc341.mcc722.gprs
> The last part of this domain is standarized by 3GPP (mncxxx.mccxxx.gprs)
the
> first three is the APN (access-point name).
Well, that's not a standard Internet gTLD, so there's not much we
can do to help you debug that problem directly.
> In our DNS we have a domain
> gprs., could this conflict with specific domain?
If you don't have a delegation for the subdomain, yes.
It's like having your server configured to think that it owns all
of .com, and not having a delegation for aol.com, and then
complaining that you can't get to AOL.
--
Brad Knowles, <brad at stop.mail-abuse.org>
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755
SAGE member since 1995. See <http://www.sage.org/> for more info.
More information about the bind-users
mailing list