Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PDNS to support Views #63

Closed
Habbie opened this issue Apr 26, 2013 · 4 comments
Closed

PDNS to support Views #63

Habbie opened this issue Apr 26, 2013 · 4 comments
Assignees
Labels

Comments

@Habbie
Copy link
Member

Habbie commented Apr 26, 2013

I was wondering if powerdns supports the concept of "views" the way ISC Bind does?

I have the following scenario:

PDNS -----> FW -----> INTERNET -----> CLIENT1
^
|
SERVER-------|

PDNS and SERVER are in the INSIDE Network (DMZ) and have private ip addresses, the problem is that when SERVER asks for a dns record PDNS should answer the A private IP address, but when CLIENT1 asks for the same record, PDNS should answer with the public IP address.

Thanks

Luciano Ramos
TelViso

@ghost ghost assigned Habbie Apr 26, 2013
@Habbie Habbie closed this as completed Apr 26, 2013
@Habbie
Copy link
Member Author

Habbie commented Apr 26, 2013

Author: ahu
Adding views would complicate the nameserver in many ways. Please run two copies of PowerDNS, they are both free!

Sorry I can't help you better.

@Sharaf5
Copy link

Sharaf5 commented Mar 28, 2024

Running many instances of the same application is no the ideal view of any thing

I'm not a C++ developer but I have a look at database structre
Screenshot_20240328_164148

But after nearly 11 years won't anything been changed ?
I could suggest to only have more one table views and more one column in records called 'views' that have views which is allowed to call for this query if no match retrun an empty response
global view should be the default

I think it's useful feature after all
using unbound with views I was able to give my local server local responses so nginx go for the desired distination and serve as reverse proxy and SSL terminator while no data is exposed
and clients could resolve separatly
all on top of 3 proccess only firewall, nginx, unbound

That even worked on a very limited resource machine
and I see that pdns is more flexable with the abilaty to use database as a backend
I was hopeful that this feature may replace unbound by pdns for me
and maybe make it an alternative to coredns with k8s

@Habbie
Copy link
Member Author

Habbie commented Mar 28, 2024

Views are actually on our roadmap now, but I don't have details yet.

@Sharaf5
Copy link

Sharaf5 commented Mar 28, 2024

Awesome news
would you open this issue agian once you have more datails
as most forums didn't mention you may support it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants