4 ms·
Ask the name server: do a AXFR query, as in host -l foo.com. These days many domains are configured to refuse AXFR queries though. Then there's a misguided but
by fulafel 8y ago
Ask the name server: do a AXFR query, as in host -l foo.com.
These days many domains are configured to refuse AXFR queries though. Then there's a misguided but common phenomenon called split-horizon DNS is also common, where you serve different records as answers to the same query based on what the query originator's address is.
- Diederich 8y ago> misguided citation needed.
- hluska 8y ago"Citation needed" comments are useless. If you disagree, state why. Otherwise, you aren't helping anyone and merely adding confusion about one of the base technologies.
- LyndsySimon 8y agoI disagree - it’s merely asking for elaboration on a stated opinion.
- reitanqild 8y agoI'd say it is a very confrontational way of asking for elaboration.
- Diederich 8y agoI've thought about this a bit, and decided that doing 'the Wikipedia thing' ('Citation Needed') was minimally confrontational, in that it's kind of a standard, somewhat 'mechanical' approach. I had no idea that some would consider it 'very confrontational'; that's the exact opposite of my intent. Speaking transparently, when I write 'Citation Needed', it's usually because I do disagree with the statement in question, but that my disagreement is not sufficiently supported. It also means that I'm open to being corrected with additional information.
- reitanqild 8y agoI guess the reason it comes off as rude is because it is so short and - for my lack of a better word - rubberstampy. It is as if some people don't have time to ask politely for sources. I also think it might trigger the "passive agressive"-detector for some people here. (I think that description has been overused a lot though and don't want to classify it as such.) This might not be your intention but I wouldn't be very sad to see those words less often here. And one more thing: using wikipedia as an example for how to behave in society might not be a good idea IMO.
- Diederich 8y agoAs I noted in another comment, when I reply 'Citation Needed', it's because I weakly disagree with the statement, but that disagreement is insufficiently supported. In many cases, I'll go off and do some independent research at the same time, but mostly I'm requesting that the person provide some additional support for their thought. It also means that I'm open to being wrong in my disagreement. So, in short, I don't state disagreement in these cases because the strength of my opinion is too weak to merit it.
- antsar 8y agoApparently there is a conflict between using DNSSEC and split-horizon. https://lists.opendnssec.org/pipermail/opendnssec-user/2012-July/002026.html https://lists.opendnssec.org/pipermail/opendnssec-user/2012-...
- fulafel 8y agoIt's just counter to the basic internet and DNS design principes and breaks many things in applications working with DNS names and IP addresses. Not to mention the added complexity and twists in troubleshooting when your names are ambiguous. The basic design of DNS is one root and same view for all.
- stephengillie 8y agoIt's refused for security reasons. This was how Valve was hacked in 2003, leading to Half Life 2's leak. > "I was scanning Valve's network to check for accessible web servers where I thought information about the game might have been held. Valve's network was reasonably secure from the outside, but the weakness was that their name server allowed anonymous AXFRs, which gave me quite a bit of information." AXFR stands for Asynchronous Full Zone Transfer, a tool used to synchronise backup DNS servers with the same data as the primary server. But it's also a protocol used by hackers to sneak a peek at a website's data. By transferring this data, Gembe was able to discover the names of all the subdomains of ValveSoftware.com. "In the port scan logs, I found an interesting server which was in Valve's network range from another corporation named Tangis that specialised in wearable computing devices," he says. "This server had a publically writable web root where I could upload ASP scripts and execute them via the web server. Valve didn't firewall this server from its internal network." https://www.eurogamer.net/articles/2011-02-21-the-boy-who-stole-half-life-2-article https://www.eurogamer.net/articles/2011-02-21-the-boy-who-st...
- fulafel 8y agoI agree it's often motivated by security reasons, but it's of rather questionable effectiveness. Don't put confidential information in the DNS, ever. Re the Valve case: this could have been also found with a simple ip range port scan, or a bunch of other ways. In the end it was just a server in the network with no access control configured and they happened to spot it in the DNS records first. "In the port scan logs, I found an interesting server which was in Valve's network range from another corporation named Tangis that specialised in wearable computing devices," he says." Also, in the modern world, you can see the web servers in a domain in the public cert transparency logs.
- mmt 8y ago> Then there's a misguided but common phenomenon called split-horizon DNS is also common, where you serve different records as answers to the same query based on what the query originator's address is. Do you consider the whole functionality of views to be misguided, or just predicating the selection of view solely on source address? I'm not sure if there's a way to handle multi-homed hosts in a more simple/elegant fashion than with views. Merely for serving distinct "internal" and "external" zones from the same server, it seems like a convenience fraught with pitfalls.
- fulafel 8y agoIt's all part of the pit you start digging yourself when you start using context dependent (eg rfc1918) addresses. Everything with the IP/Internet architecture was designed to work with globally unique addresseses.
- mmt 8y ago> Everything with the IP/Internet architecture was designed Sure, but that statement is only true in the past tense and only for a sufficiently-past definition of "everything". One could make a similar complaint about the breakdown of classful routing and subnets, but the Internet has morphed beyond its original design, in response to the realities of how it's been used [1]. Regardless, it seems your objection is to the non-global-uniqueness of private addressing, which existed well before split-dns. Is there any separate objection you have to split-dns? [1] The wisdom of each particular decision is debatable, but I, personally, find little interest in exploring alternate-history/what-if scenarios, technical or otherwise.
- fulafel 8y agoI don't really see the CIDR analogy - CIDR is in line with the end-to-end architecture and doesn't break applications using IP addresses. Anyway, consider a basic use case like an application (correctly) caching DNS records for the duration of their time-to-live metadata - and moving between networks that yield different reponses to these queries. With the added twist that different applications cache differently so now you have an incoherent view of the DNS on the same system. Another comment said it won't work with DNSSEC, that's another example stemming from going against the design and basic principles of the DNS. It's true that there are some reasonable use cases context dependent DNS replies, such CDN's returning a nearby address from a set of geographically replicated content servers, but the common internal/external split-dns setup is fundamentally unsound.