When trying to determine a country code for 200.150.7.132, I first tried
ARIN which pointed me to LACNIC - whois.lacnic.net:
inetnum: 200.128/9
status: allocated
owner: Comite Gestor da Internet no Brasil
ownerid: BR-CGIN-LACNIC
responsible: Frederico A C Neves
address: Av. das Na��es Unidas, 11541, 7� andar
address: 04578-000 - S�o Paulo - SP
country: BR
phone: +55 11 9119-0304 []
owner-c: CGB
tech-c: CGB
inetrev: 200.128/9
nserver: NS.DNS.BR
nsstat: 20031015 AA
nslastaa: 20031015
nserver: NS1.DNS.BR
nsstat: 20031015 AA
nslastaa: 20031015
nserver: NS2.DNS.BR
nsstat: 20031015 AA
nslastaa: 20031015
remarks: These addresses have been further assigned to Brazilian
users.
remarks: Contact information can be found at the WHOIS server located
remarks: at whois.registro.br and at http://whois.nic.br
So off to whois.nic.br:
inetnum: 200.150.7/24
aut-num: AS23106
abuse-c: RBS151
owner: COMPANHIA ENERGETICA DE MINAS GERAIS
ownerid: 017.155.730/0001-64
responsible: Marcus Vinicius da Silva
address: Av Barbacena, 1200, 3 Andar
address: 30190-131 - Belo Horizonte - MG
phone: (031) 349-4469 []
owner-c: MVS9
tech-c: MVS9
inetrev: 200.150.7/24
nserver: OUTCEMIG1.CEMIG.COM.BR
nsstat: 20031018 AA
nslastaa: 20031018
nserver: OUTCEMIG2.CEMIG.COM.BR
nsstat: 20031018 AA
nslastaa: 20031018
created: 20020621
changed: 20020621
inetnum-up: 200.150.0/19
Does anyone know what standard is being used here? It looks like RIPE
format but very modified. What bothers me is not the additional tags but
rather that an automated script would not be able to determine country
from their response.
These whois servers uses an output format "based" on RPSL with added
extensions for organizations and dns delegation status.
The whois server at the .BR registry (also the NIR for Brazil) doesn't
provide country information because it's implicit as it only provide
information for Brazil.
These whois servers uses an output format "based" on RPSL with added
extensions for organizations and dns delegation status.
Can you point me to documentation on the extensions? Any plan on RFCing?
The whois server at the .BR registry (also the NIR for Brazil) doesn't
provide country information because it's implicit as it only provide
information for Brazil.
Implicit is fine for humans but for automated scripts, couldn't it be made to have country=BR for all your inetnum entries?
Got something really weird going on and I need a bit of help from someone
who is really good with dns.
Domain elby.ch
seems to resolve from some DNS servers but not from others. Can you see
anything that might break dns resolution for this domain? Specifically it
appears NT4 dns servers with SecureResponses turned on. Please feel free to
answer me offlist.
NOTE: These records may be inaccurate, since the parent servers (tulku.nic.ar.) do not know the NS records for elby.ch (or give a referral to other DNS servers)! This may cause other tests not to work properly, such as the 'Nameservers on separate class C' test.
The name servers for the domain elby.ch do not reverse resolve.
For example: ns1.elbyns.de resolves to 62.116.130.76, but 62.116.130.76
does not resolve back ns1.elbyns.de.
It's not clear through the RIPE Whois search (this IP block is within a RIPE
range) who does name service for the IP block. Contact your local provider
to arrange for the IP to reverse resolve properly.
I don't see a delegation to tulku.nic.ar. anywhere down the delegation
chain.
. says ch nameservers are:
NS.APNIC.NET. 2D IN A 203.37.255.97
DOMREG.NIC.ch. 2D IN A 130.59.1.80
MERAPI.SWITCH.ch. 2D IN A 130.59.211.10
DNS.PRINCETON.EDU. 2D IN A 128.112.129.15 RIP.PSG.COM. 2D IN A 147.28.0.39
TULKU.NIC.AR. 2D IN A 200.16.97.77
CCTLD.TIX.ch. 2D IN A 194.42.48.120
all these nameservers agree that elby.ch nameservers are:
NOTE: These records may be inaccurate, since the parent servers
(tulku.nic.ar.) do not know the NS records for elby.ch (or give a referral
to other DNS servers)! This may cause other tests not to work properly,
such as the 'Nameservers on separate class C' test.
This may or may not be related to your problem.
-Hank
>seems to resolve from some DNS servers but not from others. Can you see
>anything that might break dns resolution for this domain? Specifically it
>appears NT4 dns servers with SecureResponses turned on. Please feel free to
>answer me offlist.
>
>Geo.
--mghali@snark.net------------------------------------------<darwin><
Flowers on the razor wire/I know you're here/We are few/And far
between/I was thinking about her skin/Love is a many splintered
thing/Don't be afraid now/Just walk on in. #include <disclaim.h>
Got something really weird going on and I need a bit of help
> from someone who is really good with dns.
> Domain elby.ch
> seems to resolve from some DNS servers but not from others. Can
> you see anything that might break dns resolution for this
> domain?
Yes, you've got _way_ too many levels of referrals before any glue
records show up.
The chain looks something like this:
.ch servers return referral elby.ch -> ns{1,2}.elbyns.de with no glue.
.de servers return referral elbyns.de -> ns{1,2}.aixns.de with no glue.
.de servers return referral aixns.de -> ns0.ns0.de,ns2.ns2.de with no glue.
.de servers return referral ns0.de/ns2.de -> ns*.denoc.de with glue.
When I tried it with the squish.net dns checker (turn on "show
resolving of referrals" to see the awful details of the referral
chain) I got at least one query timeout, so the results were:
10.7% of queries will end in failure at 62.116.163.62 (ns2.ns2.de) -
failed to resolve ns2.elbyns.de due to 62.116.163.62 - failed to
resolve ns1.aixns.de due to 62.116.163.62 - query timed out
10.7% of queries will end in failure at 62.116.163.62 (ns2.ns2.de) -
failed to resolve ns1.elbyns.de due to 62.116.163.62 - failed to
resolve ns1.aixns.de due to 62.116.163.62 - query timed out
39.3% of queries will be returned by 62.116.130.76 (ns1.elbyns.de)
elby.ch. 86400 IN A 213.130.59.30
39.3% of queries will be returned by 62.116.162.15 (ns2.elbyns.de)
elby.ch. 86400 IN A 213.130.59.30
But the squish.net checker has no limit on referrals - many resolvers,
especially older BIND, will just time out chasing the referrals unless
it already has them cached.
>Hank,
>
>These whois servers uses an output format "based" on RPSL with added
>extensions for organizations and dns delegation status.
Can you point me to documentation on the extensions? Any plan on RFCing?
No. There is no public documentation for this. There is an effort at
the IETF [1] trying to standardize the discovery, output format and
the query semantics. Some time in the future these servers will be
"CRISP" compliant.
>The whois server at the .BR registry (also the NIR for Brazil) doesn't
>provide country information because it's implicit as it only provide
>information for Brazil.
Implicit is fine for humans but for automated scripts, couldn't it be made
to have country=BR for all your inetnum entries?
The whois server at the .BR registry (also the NIR for Brazil) doesn't
provide country information because it's implicit as it only provide
information for Brazil.
Implicit is fine for humans but for automated scripts, couldn't it be made to have country=BR for all your inetnum entries?
When I was running a whois server we discovered that not all local people appeared to want to use a local address. Some of them had head offices used for billing, and the like, that was in a different country so having the country code was useful even for humans.
The whois server at the .BR registry (also the NIR for Brazil) doesn't
provide country information because it's implicit as it only provide
information for Brazil.
Implicit is fine for humans but for automated scripts, couldn't it be made to have country=BR for all your inetnum entries?
When I was running a whois server we discovered that not all local people appeared to want to use a local address. Some of them had head offices used for billing, and the like, that was in a different country so having the country code was useful even for humans.
So how should whois users understand country information in the database?
Should they interpret it as "my network is located in this country"? Alternatively, should they interpret it as "our corporate offices are in this country"? Increasingly, there is a discontinuity between the two as international corporations run networks in many countries from an HQ in just one.
If people updating the information in whois have different ideas about its meaning then users of whois its value might be lower than expected.