Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #272325
| From | Wesley <wesley@mxcloud.eu.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: domain status in registry and registrar |
| Date | 2024-08-20 01:10 +0200 |
| Message-ID | <JdjFE-6cA9-5@gated-at.bofh.it> (permalink) |
| References | <Jd5jj-63Ai-11@gated-at.bofh.it> <JddAd-68I6-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 2024-08-20 00:35, Andy Smith wrote:
> Hi,
>
> TL;DR: I too find it a little odd that whois says this domain is
> reserved but
> querying the DNS shows that it isn't there at all as I would
> usually expect just the NS records to be present in the containing
> zone. I can only assume that this registrar allows for registered
> zones to not be published at all if one wishes. The whois is
> authoritative for what is available to register; the DNS is
> authoritative for what you can globally query.
>
> On Mon, Aug 19, 2024 at 03:49:11PM +0800, Wesley wrote:
>> This is the dns info from registry nameserver:
>
> In future it would help if you showed what actual query you are
> doing with "dig". From the output I can piece together that you did
> something like:
>
> $ dig datafarm.net
>
> or
>
> $ dig -t s datafarm.net
>
> but assuming that indeed is what you did, it does not actually "ask
> the registry nameserver".
>
> We can see from your output that you got a response from:
>
>> ;; SERVER: 10.160.0.1#53(10.160.0.1)
>
> which is probably a resolver on your local network. So that answer
> you got may have been from cache.
>
> We can see from your output that you ended up (either implicitly or
> explicitly) asking for an A query:
>
>> ;; QUESTION SECTION:
>> ;datafarm.net. IN A
>
> However the best record to use when trying to see if a domain exists
> i*in DNS* is an SOA ("Start of Authority"). It should show where the
> domain delegation happens. It's basically the details for the DNS
> zone.
>
Andy
The dig from com's nameservers got nxdomain as well. As you see here,
$ dig datafarm.net @a.gtld-servers.net
; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> datafarm.net
@a.gtld-servers.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45385
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;datafarm.net. IN A
;; AUTHORITY SECTION:
net. 900 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1724107985
1800 900 604800 86400
;; Query time: 7 msec
;; SERVER: 2001:503:a83e::2:30#53(a.gtld-servers.net) (UDP)
;; WHEN: Tue Aug 20 06:53:27 HKT 2024
;; MSG SIZE rcvd: 114
nxdomain means this domain (zone) not existing, whether it's A record or
the zone itself. if the zone exists but lacks A record, the status
should be 'NOERROR'.
What confused me is that since domain is registered in the registrar,
they should put a glue in com's nameservers. hence com nameserver would
not return 'nxdomain' but a reference instead.
BTW, I found there are many cases like the domain 'datafarm.net'. for
example, 'netfirm.net' behaves the same.
Thank you.
--
https://wespeng.pages.dev/
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
domain status in registry and registrar Wesley <wesley@mxcloud.eu.org> - 2024-08-19 09:50 +0200
Re: domain status in registry and registrar <tomas@tuxteam.de> - 2024-08-19 10:20 +0200
Re: domain status in registry and registrar Dan Purgert <dan@djph.net> - 2024-08-19 11:00 +0200
Re: domain status in registry and registrar Bret Busby <bret@busby.net> - 2024-08-19 15:00 +0200
Re: domain status in registry and registrar <tomas@tuxteam.de> - 2024-08-19 15:10 +0200
Re: domain status in registry and registrar Bret Busby <bret@busby.net> - 2024-08-19 15:40 +0200
Re: domain status in registry and registrar Dan Ritter <dsr@randomstring.org> - 2024-08-19 16:10 +0200
Re: domain status in registry and registrar Michael Kjörling <c9bc136c6063@ewoof.net> - 2024-08-19 16:30 +0200
Re: domain status in registry and registrar Andy Smith <andy@strugglers.net> - 2024-08-19 18:40 +0200
Re: domain status in registry and registrar Michael Grant <mgrant@grant.org> - 2024-08-19 18:50 +0200
Re: domain status in registry and registrar Andy Smith <andy@strugglers.net> - 2024-08-19 21:30 +0200
Re: domain status in registry and registrar Wesley <wesley@mxcloud.eu.org> - 2024-08-20 01:10 +0200
Re: domain status in registry and registrar Andy Smith <andy@strugglers.net> - 2024-08-20 01:20 +0200
csiph-web