Re: Wildcard SRV record?

[Stephen Pape]

Yeah, as I said in one of the other emails, I can script something
with nsupdate if necessary. I was just hoping there was a way to add a
simple record that'd take care of it all, but now I understand that
wildcards don't really work that way, so I've scripted something.

I don't have separate zones for each of the domains; rather there's a
single top level "foo" zone. A and Ptr records are added via
DHCP/rndc, and DHCP assigns "username.foo" domain names.

My approach feels a bit "hackish" to me. Now I have several hundred
CNAME records in the .foo zone, all pointing to the same SRV record.
I'll have to deal with removing old records as users are removed, and
I'll have to make sure the script runs reliably, but it works.

I appreciate the help, anyway!

-Stephen

On Mon, Oct 31, 2016 at 6:04 PM, Mark Andrews  wrote:
>
> In message 
> 

Re: Wildcard SRV record?

[Stephen Pape]

That doesn't work for me. When machine1.domain1.foo tries to look up
the SRV record, it queries for _vlmcs._tcp.domain1.foo. Bind doesn't
have that record, so it doesn't work.

On Mon, Oct 31, 2016 at 1:08 PM, Eldridge, Rod A [ITNET]
<r...@iastate.edu> wrote:
>
> Wouldn't you just need this one SRV record:
>
> _vlmcs._tcp.foo IN SRV 0 0 1688 ais-dc01.ainfosec.com.
>
> [ see 
> https://blogs.technet.microsoft.com/odsupport/2011/11/14/how-to-discover-office-and-windows-kms-hosts-via-dns-and-remove-unauthorized-instances/
>  ]
>
>
> --
> Rod Eldridge
> Networks & Communications
> IT Services, Iowa State University of Science and Technology
>
>
>
>> On Oct 31, 2016, at 11:35 AM, Stephen Pape <srp...@gmail.com> wrote:
>>
>> Hello all,
>>
>> I have bind configured with a single TLD (.foo), and inside that are
>> records for a large number of subdomains (machine1.a.foo,
>> machine2.a.foo, machine1.b.foo, machine2.b.foo, etc.). DHCP clients
>> are assigned a domain based on some factors, but it might be a.foo,
>> b.foo, c.foo, etc.
>>
>> I'm trying to add a SRV record for everyone under .foo. I've tried:
>>
>> _vlmcs._tcp.*.foo.IN  SRV 0 0 1688 ais-dc01.ainfosec.com.
>>
>> ... but it seems that wildcards don't work that way. I've tried
>> something similar with CNAMEs, but that didn't work either.
>>
>> What DOES work is adding a CNAME record for each and every domain that
>> I need. So a CNAME for _vlmcs._tcp.a.foo, _vlmcs._tcp.b.foo, etc.
>>
>> Is there a better way for me to do this, or do I have to generate a
>> whole lot of specific CNAME records?
>>
>> Thanks!
>>
>> -Stephen
>> ___
>> 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
>
___
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: Wildcard SRV record?

[Stephen Pape]

Thanks, but the names aren't predictable; they're usernames. I could
script something with nsupdate, if necessary, but I'd rather have a
simple record than have scripting/cron.

On Mon, Oct 31, 2016 at 12:44 PM, Matthew Pounsett <m...@conundrum.com> wrote:
>
>
> On 31 October 2016 at 12:35, Stephen Pape <srp...@gmail.com> wrote:
>>
>> Is there a better way for me to do this, or do I have to generate a
>> whole lot of specific CNAME records?
>
>
> If your subdomains follow a predictable pattern, then this seems like a
> prime use of the $GENERATE statement.  You could either use it to generate
> the CNAMEs, or directly generate the SRV records themselves.
>
>
>
___
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