Re: nslookup oddities (Was: SRV record not working)
On 08/20/2018 10:14 AM, Lee wrote: On 8/19/18, Mark Andrews wrote: nslookup applies the search list by default and doesn’t stop on a NODATA response. Some versions of nslookup have been modified by OS vendors to use /etc/hosts for address lookups. nslookup doesn’t display the entire response by default. I learned something :) Thank you Not that I know the implications of "doesn’t stop on a NODATA response" but hopefully that can be remedied. wrt the search list, that's why I got in the habit of always typing the trailing dot. I've never seen that fail, but 'set nosearch' is supposed to do the same thing. 'set debug' and 'set d2' displays lots, but I never checked to see if it was the entire response or no So... it seems like the bottom line is that dig is better but nslookup ain't all that bad Lee, Messages like this, and the one you sent me privately, are the reason that I usually don't even bother replying to messages on this list. I don't say that to denigrate you. I say it in the hopes that someone, maybe even you, will learn from your mistake. Your "bottom line" completely misses basically everything that's been said in this thread. No one has made any statement about nslookup being "bad," or "worse" than any other tool. I have clearly stated the contexts in which the two tools are more or less suited for a given situation, and given reasons why. Others have expanded on those reasons. If you still don't understand why, at least try to understand the when and how. Go back and re-read the thread. Look up the terms that you don't understand. You can even ask reasonable, specific questions to the effect of, "I looked up term XYZ but didn't understand how the zig interacts with the zag, can someone explain that to me?" In other words, do SOMETHING to help yourself. Don't complain that no one worked hard enough to make you understand something that you seem to be working so hard to misunderstand. Good luck, Doug ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: nslookup oddities (Was: SRV record not working)
Lee wrote: > > So... it seems like the bottom line is that dig is better but nslookup > ain't all that bad Be careful though, all bets are off if you find yourself using something that claims to be nslookup but which isn't the BIND9 version. Tony. -- f.anthony.n.finchhttp://dotat.at/ North Rockall, Malin, Hebrides, Bailey, Fair Isle, Faeroes: Variable 3 or 4, becoming southeasterly 4 or 5, then cyclonic, mainly southerly or southwesterly later, 5 to 7. Moderate, occasionally rough later. Fair then rain with fog patches. Good becoming moderate, occasionally very poor. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: nslookup oddities (Was: SRV record not working)
On 8/19/18, Mark Andrews wrote: > nslookup applies the search list by default and doesn’t stop on a NODATA > response. > > Some versions of nslookup have been modified by OS vendors to use /etc/hosts > for address lookups. > > nslookup doesn’t display the entire response by default. I learned something :) Thank you Not that I know the implications of "doesn’t stop on a NODATA response" but hopefully that can be remedied. wrt the search list, that's why I got in the habit of always typing the trailing dot. I've never seen that fail, but 'set nosearch' is supposed to do the same thing. 'set debug' and 'set d2' displays lots, but I never checked to see if it was the entire response or no So... it seems like the bottom line is that dig is better but nslookup ain't all that bad Thanks Lee >> On 20 Aug 2018, at 12:28 pm, Lee wrote: >> >> On 8/19/18, Doug Barton wrote: >>> On 08/19/2018 12:11 PM, Lee wrote: On 8/18/18, Doug Barton wrote: >>> > nslookup uses the local resolver stub. That's fine, if that's what you > want/need to test. If you want to test specific servers, or what is > visible from the Internet, etc. dig is the right tool, as the answers > you get from nslookup cannot be guaranteed to be directly related to > the > question you asked. Could you expand on that a bit please? I thought nslookup was pretty much equivalent to dig @ the exception being that nslookup looks for a & records and dig just looks for a records >>> >>> Nope. Depending on what operating system you're on, what version of >>> nslookup you have, how you format your query, and how the system is >>> configured; even telling nslookup to query a specific server may not get >>> you the answer you're looking for. >> >> That's still awfully vague. Do you have any examples of >>nslookup >> returning bad information? >> >>> If you want to know what answer your stub resolver is going to return >>> for a given query, nslookup is a great tool. Although, if you just need >>> to know what address record you'll get back, ping works just as well. >> >> ping just shows one address; "nslookup www.yahoo.com" shows all of them >> >>> If you want to really debug DNS you need to learn to use dig, and >>> understand the output. >> >> Agreed. If you're serious about debugging DNS you needs to learn dig. >> But the assertion is > ... the answers > you get from nslookup cannot be guaranteed to be directly related to > the > question you asked. >> >> so I'm wondering how, or under what circumstances, nslookup returns >> invalid information. >> >> Thanks >> Lee ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: nslookup oddities (Was: SRV record not working)
And don't forget NIS, and NSSwitch. And don't get me started on the tricks that the windows resolver plays. On 08/19/2018 07:59 PM, Mark Andrews wrote: nslookup applies the search list by default and doesn’t stop on a NODATA response. Some versions of nslookup have been modified by OS vendors to use /etc/hosts for address lookups. nslookup doesn’t display the entire response by default. On 20 Aug 2018, at 12:28 pm, Lee wrote: On 8/19/18, Doug Barton wrote: On 08/19/2018 12:11 PM, Lee wrote: On 8/18/18, Doug Barton wrote: nslookup uses the local resolver stub. That's fine, if that's what you want/need to test. If you want to test specific servers, or what is visible from the Internet, etc. dig is the right tool, as the answers you get from nslookup cannot be guaranteed to be directly related to the question you asked. Could you expand on that a bit please? I thought nslookup was pretty much equivalent to dig @ the exception being that nslookup looks for a & records and dig just looks for a records Nope. Depending on what operating system you're on, what version of nslookup you have, how you format your query, and how the system is configured; even telling nslookup to query a specific server may not get you the answer you're looking for. That's still awfully vague. Do you have any examples of nslookup returning bad information? If you want to know what answer your stub resolver is going to return for a given query, nslookup is a great tool. Although, if you just need to know what address record you'll get back, ping works just as well. ping just shows one address; "nslookup www.yahoo.com" shows all of them If you want to really debug DNS you need to learn to use dig, and understand the output. Agreed. If you're serious about debugging DNS you needs to learn dig. But the assertion is ... the answers you get from nslookup cannot be guaranteed to be directly related to the question you asked. so I'm wondering how, or under what circumstances, nslookup returns invalid information. Thanks Lee ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: nslookup oddities (Was: SRV record not working)
nslookup applies the search list by default and doesn’t stop on a NODATA response. Some versions of nslookup have been modified by OS vendors to use /etc/hosts for address lookups. nslookup doesn’t display the entire response by default. > On 20 Aug 2018, at 12:28 pm, Lee wrote: > > On 8/19/18, Doug Barton wrote: >> On 08/19/2018 12:11 PM, Lee wrote: >>> On 8/18/18, Doug Barton wrote: >> nslookup uses the local resolver stub. That's fine, if that's what you want/need to test. If you want to test specific servers, or what is visible from the Internet, etc. dig is the right tool, as the answers you get from nslookup cannot be guaranteed to be directly related to the question you asked. >>> >>> Could you expand on that a bit please? I thought >>> nslookup >>> was pretty much equivalent to >>> dig @ >>> >>> the exception being that nslookup looks for a & records and dig >>> just looks for a records >> >> Nope. Depending on what operating system you're on, what version of >> nslookup you have, how you format your query, and how the system is >> configured; even telling nslookup to query a specific server may not get >> you the answer you're looking for. > > That's still awfully vague. Do you have any examples of >nslookup > returning bad information? > >> If you want to know what answer your stub resolver is going to return >> for a given query, nslookup is a great tool. Although, if you just need >> to know what address record you'll get back, ping works just as well. > > ping just shows one address; "nslookup www.yahoo.com" shows all of them > >> If you want to really debug DNS you need to learn to use dig, and >> understand the output. > > Agreed. If you're serious about debugging DNS you needs to learn dig. > But the assertion is ... the answers you get from nslookup cannot be guaranteed to be directly related to the question you asked. > > so I'm wondering how, or under what circumstances, nslookup returns > invalid information. > > Thanks > Lee > ___ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: nslookup oddities (Was: SRV record not working)
On 8/19/18, Doug Barton wrote: > On 08/19/2018 12:11 PM, Lee wrote: >> On 8/18/18, Doug Barton wrote: > >>> nslookup uses the local resolver stub. That's fine, if that's what you >>> want/need to test. If you want to test specific servers, or what is >>> visible from the Internet, etc. dig is the right tool, as the answers >>> you get from nslookup cannot be guaranteed to be directly related to the >>> question you asked. >> >> Could you expand on that a bit please? I thought >>nslookup >> was pretty much equivalent to >> dig @ >> >> the exception being that nslookup looks for a & records and dig >> just looks for a records > > Nope. Depending on what operating system you're on, what version of > nslookup you have, how you format your query, and how the system is > configured; even telling nslookup to query a specific server may not get > you the answer you're looking for. That's still awfully vague. Do you have any examples of nslookup returning bad information? > If you want to know what answer your stub resolver is going to return > for a given query, nslookup is a great tool. Although, if you just need > to know what address record you'll get back, ping works just as well. ping just shows one address; "nslookup www.yahoo.com" shows all of them > If you want to really debug DNS you need to learn to use dig, and > understand the output. Agreed. If you're serious about debugging DNS you needs to learn dig. But the assertion is >>> ... the answers >>> you get from nslookup cannot be guaranteed to be directly related to the >>> question you asked. so I'm wondering how, or under what circumstances, nslookup returns invalid information. Thanks Lee ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: nslookup oddities (Was: SRV record not working)
On 08/19/2018 12:11 PM, Lee wrote: On 8/18/18, Doug Barton wrote: nslookup uses the local resolver stub. That's fine, if that's what you want/need to test. If you want to test specific servers, or what is visible from the Internet, etc. dig is the right tool, as the answers you get from nslookup cannot be guaranteed to be directly related to the question you asked. Could you expand on that a bit please? I thought nslookup was pretty much equivalent to dig @ the exception being that nslookup looks for a & records and dig just looks for a records Nope. Depending on what operating system you're on, what version of nslookup you have, how you format your query, and how the system is configured; even telling nslookup to query a specific server may not get you the answer you're looking for. If you want to know what answer your stub resolver is going to return for a given query, nslookup is a great tool. Although, if you just need to know what address record you'll get back, ping works just as well. If you want to really debug DNS you need to learn to use dig, and understand the output. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: SRV record not working
On 8/18/18, Doug Barton wrote: > On 08/18/2018 04:53 PM, Barry Margolin wrote: >> In article , >> Grant Taylor wrote: >> >>> On 08/18/2018 07:25 AM, Bob McDonald wrote: I don't think anyone hates nslookup (well maybe a few do ) I suppose the immense dislike stems from the fact that it's the default utility under Windows. Folks who use dig as their default realize that when used properly, dig provides much more functionality than nslookup. For example, try using TSIG with nslookup or getting a NSID response. These are only a couple of examples. There's other reasons to change. The output from dig is much more comprehensive. And, yes, if you install the bind tools from ISC under Windows, dig works quite well. >>> >>> I've been told that nslookup will lie and provide incorrect information >>> in some situations. I have no idea what situations that is. I would >>> love to learn what they are. >>> >>> If you know of such an example, please enlighten me. >>> >>> As such, I tend to use nslookup on platforms without dig when or until I >>> have reason to not do so. >> >> I don't think it "lies" much, but the output isn't as clear and >> unambiguous as dig's. When it reports errors, it can be difficult to >> tell specifically what the actual error was. >> >> One example I can think of is that for some reason it expects the >> nameserver to be able to reverse-resolve its own IP. If it can't, it >> reports this as an error, and you might think that it's reporting an >> error about the name you're actually trying to look up. > > nslookup uses the local resolver stub. That's fine, if that's what you > want/need to test. If you want to test specific servers, or what is > visible from the Internet, etc. dig is the right tool, as the answers > you get from nslookup cannot be guaranteed to be directly related to the > question you asked. Could you expand on that a bit please? I thought nslookup was pretty much equivalent to dig @ the exception being that nslookup looks for a & records and dig just looks for a records Thanks, Lee ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: SRV record not working
On 08/18/2018 04:53 PM, Barry Margolin wrote: In article , Grant Taylor wrote: On 08/18/2018 07:25 AM, Bob McDonald wrote: I don't think anyone hates nslookup (well maybe a few do ) I suppose the immense dislike stems from the fact that it's the default utility under Windows. Folks who use dig as their default realize that when used properly, dig provides much more functionality than nslookup. For example, try using TSIG with nslookup or getting a NSID response. These are only a couple of examples. There's other reasons to change. The output from dig is much more comprehensive. And, yes, if you install the bind tools from ISC under Windows, dig works quite well. I've been told that nslookup will lie and provide incorrect information in some situations. I have no idea what situations that is. I would love to learn what they are. If you know of such an example, please enlighten me. As such, I tend to use nslookup on platforms without dig when or until I have reason to not do so. I don't think it "lies" much, but the output isn't as clear and unambiguous as dig's. When it reports errors, it can be difficult to tell specifically what the actual error was. One example I can think of is that for some reason it expects the nameserver to be able to reverse-resolve its own IP. If it can't, it reports this as an error, and you might think that it's reporting an error about the name you're actually trying to look up. nslookup uses the local resolver stub. That's fine, if that's what you want/need to test. If you want to test specific servers, or what is visible from the Internet, etc. dig is the right tool, as the answers you get from nslookup cannot be guaranteed to be directly related to the question you asked. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: SRV record not working
In article , Grant Taylor wrote: > On 08/18/2018 07:25 AM, Bob McDonald wrote: > > I don't think anyone hates nslookup (well maybe a few do ) I > > suppose the immense dislike stems from the fact that it's the default > > utility under Windows. Folks who use dig as their default realize that > > when used properly, dig provides much more functionality than nslookup. > > For example, try using TSIG with nslookup or getting a NSID response. > > These are only a couple of examples. There's other reasons to change. > > The output from dig is much more comprehensive. And, yes, if you install > > the bind tools from ISC under Windows, dig works quite well. > > I've been told that nslookup will lie and provide incorrect information > in some situations. I have no idea what situations that is. I would > love to learn what they are. > > If you know of such an example, please enlighten me. > > As such, I tend to use nslookup on platforms without dig when or until I > have reason to not do so. I don't think it "lies" much, but the output isn't as clear and unambiguous as dig's. When it reports errors, it can be difficult to tell specifically what the actual error was. One example I can think of is that for some reason it expects the nameserver to be able to reverse-resolve its own IP. If it can't, it reports this as an error, and you might think that it's reporting an error about the name you're actually trying to look up. -- Barry Margolin Arlington, MA ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: SRV record not working
Extra complexity -- "man dig" yields 289 lines while "man nslookup" yields only 160 lines. Also, dig is not simply an extension of nslookup (which I long ago abbreviated to nsl), but is significantly different, so it using it involves the human analog of a cache miss. On Sat, 18 Aug 2018 20:12:01 +0200 Reindl Harald wrote: > > > Am 18.08.2018 um 20:02 schrieb Paul Kosinski: > > When I started using Linux almost 20 years ago, I think there was > > only nslookup, and no dig. So by habit, I tend to use it unless the > > extra power of dig outweighs its extra complexity. > > which extra complexity? > > because you have to add an @ when you want to use a non-default > nameserver and that you need "dig -X" for a reverse-lookup? > > you can use dig as nslookup, it's not required that you add a record > type - just "dig whatever" which is in that case even shorter > > > On Sat, 18 Aug 2018 11:42:20 -0600 > > Grant Taylor via bind-users wrote: > > > >> On 08/18/2018 07:25 AM, Bob McDonald wrote: > >>> I don't think anyone hates nslookup (well maybe a few do ) > >>> I suppose the immense dislike stems from the fact that it's the > >>> default utility under Windows. Folks who use dig as their default > >>> realize that when used properly, dig provides much more > >>> functionality than nslookup. For example, try using TSIG with > >>> nslookup or getting a NSID response. These are only a couple of > >>> examples. There's other reasons to change. The output from dig is > >>> much more comprehensive. And, yes, if you install the bind tools > >>> from ISC under Windows, dig works quite well. > >> > >> I've been told that nslookup will lie and provide incorrect > >> information in some situations. I have no idea what situations > >> that is. I would love to learn what they are. > >> > >> If you know of such an example, please enlighten me. > >> > >> As such, I tend to use nslookup on platforms without dig when or > >> until I have reason to not do so > > ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: SRV record not working
When I started using Linux almost 20 years ago, I think there was only nslookup, and no dig. So by habit, I tend to use it unless the extra power of dig outweighs its extra complexity. I don't remember what I used on Windows back when I was regularly using both. On Sat, 18 Aug 2018 11:42:20 -0600 Grant Taylor via bind-users wrote: > On 08/18/2018 07:25 AM, Bob McDonald wrote: > > I don't think anyone hates nslookup (well maybe a few do ) I > > suppose the immense dislike stems from the fact that it's the > > default utility under Windows. Folks who use dig as their default > > realize that when used properly, dig provides much more > > functionality than nslookup. For example, try using TSIG with > > nslookup or getting a NSID response. These are only a couple of > > examples. There's other reasons to change. The output from dig is > > much more comprehensive. And, yes, if you install the bind tools > > from ISC under Windows, dig works quite well. > > I've been told that nslookup will lie and provide incorrect > information in some situations. I have no idea what situations that > is. I would love to learn what they are. > > If you know of such an example, please enlighten me. > > As such, I tend to use nslookup on platforms without dig when or > until I have reason to not do so. > > > ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: SRV record not working
On 08/18/2018 07:25 AM, Bob McDonald wrote: I don't think anyone hates nslookup (well maybe a few do ) I suppose the immense dislike stems from the fact that it's the default utility under Windows. Folks who use dig as their default realize that when used properly, dig provides much more functionality than nslookup. For example, try using TSIG with nslookup or getting a NSID response. These are only a couple of examples. There's other reasons to change. The output from dig is much more comprehensive. And, yes, if you install the bind tools from ISC under Windows, dig works quite well. I've been told that nslookup will lie and provide incorrect information in some situations. I have no idea what situations that is. I would love to learn what they are. If you know of such an example, please enlighten me. As such, I tend to use nslookup on platforms without dig when or until I have reason to not do so. -- Grant. . . . unix || die smime.p7s Description: S/MIME Cryptographic Signature ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
re: SRV record not working
> I know that most of you hate nslookup but I have been using it since the > 90's and it's my go-to utility. I get the same responses whether I use > Dig or nslookup. If nslookup doesn't return what I am looking for, I do > use Dig also. I don't think anyone hates nslookup (well maybe a few do ) I suppose the immense dislike stems from the fact that it's the default utility under Windows. Folks who use dig as their default realize that when used properly, dig provides much more functionality than nslookup. For example, try using TSIG with nslookup or getting a NSID response. These are only a couple of examples. There's other reasons to change. The output from dig is much more comprehensive. And, yes, if you install the bind tools from ISC under Windows, dig works quite well. Just my $.02 Bob ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: SRV record not working
Seems ok here using: dig +trace srv _minecraft._tcp.skyblock.mc-game.us. mc-game.us. 3600IN NS ns1.sleepyvalley.net. mc-game.us. 3600IN NS sdns2.ovh.ca. ;; Received 113 bytes from 156.154.126.70#53(156.154.126.70) in 168 ms _minecraft._tcp.skyblock.mc-game.us. 300 IN SRV 0 5 25567 skyblock.mc-game.us. ;; Received 92 bytes from 167.114.154.31#53(167.114.154.31) in 73 ms On Fri, Aug 17, 2018 at 10:42 AM, Carl Byington wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On Fri, 2018-08-17 at 12:27 -0500, Thomas Strike wrote: > > I need a 2nd pair of eyes on this one. > > Works for me. > > dig _minecraft._tcp.skyblock.mc-game.us srv > > ;; ANSWER SECTION: > _minecraft._tcp.skyblock.mc-game.us. 300 IN SRV 0 5 25567 skyblock.mc- > game.us. > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.14 (GNU/Linux) > > iEYEAREKAAYFAlt3CPAACgkQL6j7milTFsHoywCfRQIVqUZnycWdYGdRupaSEWiU > ZlsAn18No1vPczhoAURmolzbt3Z+I7PU > =EQx5 > -END PGP SIGNATURE- > > > > ___ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > unsubscribe from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users > -- Peace, Joe "Without love in the dream It will never come true" Words by Robert Hunter ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
SRV record not working
Thanks all for your quick response. I didn't need a 2nd pair of eyes, I needed a 2nd brain. I didn't think that I had to use the fully qualified domain name and was just using the subdomain.domain.name for the queries. What can I say, I'm old and going senile. Your responses showed me the error of my ways. My record was working, I wasn't. Thanks again everyone. p.s. I know that most of you hate nslookup but I have been using it since the 90's and it's my go-to utility. I get the same responses whether I use Dig or nslookup. If nslookup doesn't return what I am looking for, I do use Dig also. ;I have created a SRV record for a new subdomain A record. I set ;nslookup to use my DNS server directly and when I query for the A ;record it returns it. When I set type=SRV and ask for the srv record ;nothing is returned. ;My SRV record: _minecraft._tcp.skyblock.mc-game.us. IN SRV 0 5 ;25567 skyblock.mc-game.us. ;I need a 2nd pair of eyes on this one. ;Thanks, Tom Strike ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: SRV record not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2018-08-17 at 12:27 -0500, Thomas Strike wrote: > I need a 2nd pair of eyes on this one. Works for me. dig _minecraft._tcp.skyblock.mc-game.us srv ;; ANSWER SECTION: _minecraft._tcp.skyblock.mc-game.us. 300 IN SRV 0 5 25567 skyblock.mc- game.us. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEAREKAAYFAlt3CPAACgkQL6j7milTFsHoywCfRQIVqUZnycWdYGdRupaSEWiU ZlsAn18No1vPczhoAURmolzbt3Z+I7PU =EQx5 -END PGP SIGNATURE- ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: SRV record not working
On Fri, Aug 17, 2018 at 1:28 PM Thomas Strike wrote: > I have created a SRV record for a new subdomain A record. I set nslookup > to use my DNS server directly and when I query for the A record it > returns it. When I set type=SRV and ask for the srv record nothing is > returned. > > My SRV record: _minecraft._tcp.skyblock.mc-game.us.IN SRV0 5 > 25567 skyblock.mc-game.us. > > I need a 2nd pair of eyes on this one. > > Thanks, Tom Strike > > Works for me: nslookup -q=srv _minecraft._tcp.skyblock.mc-game.us. 8.8.8.8 Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: _minecraft._tcp.skyblock.mc-game.us service = 0 5 25567 skyblock.mc-game.us. Authoritative answers can be found from: dig srv _minecraft._tcp.skyblock.mc-game.us. @8.8.8.8 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> srv _minecraft._tcp.skyblock.mc-game.us. @ 8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53437 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;_minecraft._tcp.skyblock.mc-game.us. IN SRV ;; ANSWER SECTION: _minecraft._tcp.skyblock.mc-game.us. 299 IN SRV 0 5 25567 skyblock.mc-game.us. ;; Query time: 56 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Fri Aug 17 13:38:35 EDT 2018 ;; MSG SIZE rcvd: 103 -- Bob Harold ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
SRV record not working
I have created a SRV record for a new subdomain A record. I set nslookup to use my DNS server directly and when I query for the A record it returns it. When I set type=SRV and ask for the srv record nothing is returned. My SRV record: _minecraft._tcp.skyblock.mc-game.us. IN SRV 0 5 25567 skyblock.mc-game.us. I need a 2nd pair of eyes on this one. Thanks, Tom Strike ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
