Re: [Pdns-users] SRV records - wow, hounded for payment already?
Plus 1 for steve. I am a happy powerdns user too. Subscribed to this mailing list for a couple of years. Seen a lot of newbe questions and a lot of people have done their best to help each and everyone. For free. you ask for help. You don't demand it here! Kind Regards Mr E. Op zo 5 mrt. 2017 om 18:29 schreef Steve Atkins > > > > On Mar 5, 2017, at 9:22 AM, NoBloat wrote: > > > > > > Wow, only a few days into trying pdns and I'm getting hounded about > buying support and being given a hard time about wanting to remain > anonymous which most anyone should want to anyhow. > > > > > > Yes, DNS records are public but I don't have to say which domains I'm > working on in mailing lists or forums if I don't want to and you don't have > to help if you don't want to. No one is forcing anyone to help anyone so > why even point such a lame thing out. Just don't help then. > > > > Every post you make to a mailing list goes to hundreds or thousands of > people. You're costing them a significant amount of time and attention. > > > > If you're not prepared to share the information that people need to help > you (which includes how you have replication configured, as well as the > domain involved) then you're mostly just wasting their time - which is > rude, unprofessional behaviour. > > > > You might want to take a step back and think about whether if someone else > were behaving the way you are you'd want to go out of your way to give them > free support? And whether - as a bind expert - you'd be able to diagnose > their misconfiguration without access to their bind configuration and > without the ability to query their bind server? And, even if you were able, > how much additional work that would require? > > > > (Disclaimer: I have no connection with powerdns other than being a happy > user, and one who has received very effective support here in the past.) > > > > Cheers, > > Steve > > > > > > > > As I have said, pdns is new to me, I've used to using BIND for many > years. I cannot jump into paying for support when I am simply trying to > make a case to my bosses that maybe they should consider using this product > for their enterprise networks, they would think I am a fool for suggesting > this without even playing with it for a while first to make my case. > > > > > > I'll either go back to BIND if I will continuously be told such things > when asking for basic help or I'll find one of our devs who knows the > product. I just wanted to get some hands on time with it first. > > > > > > > > > > > > - Original Message - > > > From: "Brian Candler" > > > To: "NoBloat" , Pdns-users@mailman.powerdns.com > > > Sent: Saturday, March 4, 2017 3:48:40 PM > > > Subject: Re: [Pdns-users] SRV records do not transfer correctly > > > > > > On 04/03/2017 18:56, NoBloat wrote: > > >> I'm not sure what you mean by 'what form of replication'. What > information could I give which would answer this? > > > > > > Well, you could give the type of replication you have configured! > > > > > > See: > > > https://doc.powerdns.com/md/authoritative/modes-of-operation/ > > > > > > If you are using pdns with mysql backend, then I'd say the best way is > > > to use native mysql replication between the backends. > > > > > > You can do zone transfers instead, but it requires more configuration, > > > as described in the page linked above. > > > > > >> In terms of obfuscating, sorry but all I obfuscated was the actually > domain name. The rest of the records show clearly. I cannot post private > information which I do not own. > > > > > > The DNS is a public database. > > > > > > The support policy for powerdns is clear, and Bert pointed you to it > > > already: > > > > > > > https://blog.powerdns.com/2016/01/18/open-source-support-out-in-the-open/ > > > > > > Basicaly: if you want private support, you can pay for it. If you want > free > > > support, then you publish the information about the domain you are > > > having problems with, without obfuscation. > > > > > > Most of your questions could be answered in a few seconds if you gave > the actual domains > > > and we could send queries to your servers. > > > > > > ___ > > > Pdns-users mailing list > > > Pdns-users@mailman.powerdns.com > > > https://mailman.powerdns.com/mailman/listinfo/pdns-users > > > > ___ > > Pdns-users mailing list > > Pdns-users@mailman.powerdns.com > > https://mailman.powerdns.com/mailman/listinfo/pdns-users > > ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Comments requested regarding autoserial
We do not use this function, because it was poorly documented we wrote our own serialnumber update. That said, we vote for #2 If it would be a correct and supported feature, would it still be able to do it yourself? Regards, Emiel. On Wed, Jul 15, 2015 at 4:43 AM, Curtis Maurand wrote: > Keep it and please document it. It makes updating a zone a snap. > > --Curtis > > On 7/14/2015 7:56 AM, Pieter Lexis wrote: > > Hi All, > > We'd like to have your input on a topic we've been discussing > internally. In its current state, the autoserial functionality is > somewhat incomplete, badly documented and non-intuitive to use. > > As such, we're currently on the fence on what to do with this feature. > In our opinion there are 2 options for autoserial going forward to > PowerDNS 4.0: > > 1. Removal of the functionality > 2. Making it a correct and supported feature > > As such, we'd like to have your input on this topic. Do you use the > autoserial functionality? If so, tell us how you us it. > > You can comment on this issue either by replying to this email, or if > you prefer in private by emailing to powerdns.id...@powerdns.com. > > > > -- > Curtis Maurand > cur...@maurand.com > 207-252-7748 > > ___ > Pdns-users mailing list > Pdns-users@mailman.powerdns.com > http://mailman.powerdns.com/mailman/listinfo/pdns-users > > ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] ddos
Hi Everybody, Just to be sure, is powerdns safe for the recent ddos attacks in the netherlands which used some dns malfunction? Regards, Emiel. ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] wildcard dns record behaviour
Hi, What's the correct behaviour of wildcard dns records? I have this : *.domain.com A 1.1.1.1 *.sub1.domain.com A 2.2.2.2 *.sub2.domain.com A 3.3.3.3 When I ping sub1.domain.com I get the ip 1.1.1.1 When I ping sub2.domain.com I get nothing. If I get the RFC right both should return nothing. Regards, Emiel. ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] pdns slave
The manual warns about possible strange behaviour with this trailing dot business. When I do a dig to my dns servers everything seems o.k. But will it be o.k. in six months? When I setup a master or native domain we don't put in the trailing dot and we follow the manual. (SOA : ns1.danego.net n...@danego.net 2012010101 etc) All this is working and doing as I think it should. Then I add a slave domain (or a superslave, doesn't matter behaviour is the same) PowerDNS gets an incoming zone transfer. all records that have the trailing dot appear in the database without this trailing dot. except for the SOA record. I know that on DNS level there should be a trailing dot. And yes I know powerdns adds this trailing dot when I do a dig. but WHY do I have slaved NS and MX records in the powerdns database without this trailing dot and why does the SOA have this trailing dot? my concern is the warning in the manual, expect STRANGE behaviour if you add trailing dots in the powerdns database. On Tue, May 22, 2012 at 3:02 PM, k...@rice.edu wrote: > On Tue, May 22, 2012 at 10:59:22AM +0200, Emiel van Berlo wrote: >> o.k. then why doesn't the slaved NS and MX records have this trailing >> dot in the powerdns database? >> > > The server adds them. You do not need to add a dot "." to every record > in a database, if the software can do it. It matches a user's experience > with browsers, e.g. http://www.google.com is what they enter and see > although the full correct DNS name ends with a dot ".". > > Cheers, > Ken > >> >> On Tue, May 22, 2012 at 10:46 AM, Marc Haber >> wrote: >> > On Tue, May 22, 2012 at 10:17:24AM +0200, Emiel van Berlo wrote: >> >> The PowerDNS manual has a BIG warning that it's forbidden to have a >> >> trailing dot on domainnames. >> > >> > I guess that means the internal database format. To my understanding, >> > the period must be present in the DNS packet. >> > >> >> To my opinion, something goes wrong with the slave setup and the zone >> >> transfer, or the manual is outdated. >> > >> > I think you have misunderstood. When you directly write into the >> > databases, using a trailing period is contraproductive. >> > >> > Greetings >> > Marc >> > ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] pdns slave
o.k. then why doesn't the slaved NS and MX records have this trailing dot in the powerdns database? On Tue, May 22, 2012 at 10:46 AM, Marc Haber wrote: > On Tue, May 22, 2012 at 10:17:24AM +0200, Emiel van Berlo wrote: >> The PowerDNS manual has a BIG warning that it's forbidden to have a >> trailing dot on domainnames. > > I guess that means the internal database format. To my understanding, > the period must be present in the DNS packet. > >> To my opinion, something goes wrong with the slave setup and the zone >> transfer, or the manual is outdated. > > I think you have misunderstood. When you directly write into the > databases, using a trailing period is contraproductive. > > Greetings > Marc > > -- > - > Marc Haber | "I don't trust Computers. They | Mailadresse im Header > Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 31958061 > Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062 ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] pdns slave
Hi, We have setup a PowerDNS 3.1 server and have added a slave zone. The master is on a windows 2008 dns. There is some confusion with the SOA. In PowerDNS the SOA from the slave zone has this value : ns2.danego.net. noc.danego.net. 2010110341 28800 1800 86400 86400 We read this warning from the manual about the record types: http://doc.powerdns.com/types.html "...Hostnames are NEVER terminated with a dot..." The slaved MX / CNAME records don't have this terminated dot in the database. And when we setup a Master or Native domain we create a SOA like this ns2.danego.net n...@danego.net 2010110341 28800 1800 86400 86400 Is it safe to use PowerDNS as a slave when the SOA isn't correctly formatted? Is the manual outdated and are these trailing dots no longer an issue? Regards, Emiel. ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] geo
Hi, We are new with PowerDNS and have a working lab environment with our own gui front on PowerDNS version 3.0.1. We read about the geo backend in PowerDNS version 2.9.x. There is very little we can find for PowerDNS version 3. Does PowerDNS version 3 still have geo capabilities? If so, where can we find information how to enable/use this with version 3. Regards, Emiel. ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] SOA Slave Retrieval
Hi, We are migrating to PowerDNS and I notice some strange behaviour when useing PowerDNS as a slave server. OS : CentOS 5.8 x64 PowerDNS 3.0.1 with mysql backend. Precompiled rpm from Kees Monshouwer's site Our primary bind server has this soa record : ns1.domain.tld. hostmaster.domain.tld. 2012010101 28800 1800 86400 86400 after a transfer to powerdns I expected ns1.domain.tld hostmas...@domain.tld 2012010101 28800 1800 86400 86400 (no ending dots on both domainnames and an @ in the email address) But I get exactly the same soa on powerdns as the one on the bind server. The other records, like the mx record show a domainname without the ending dot as expected. Is this normal behaviour for a slave setup? Regards, Emiel. ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
