[GH-ISSUE #24] Setting up a domain #18

Closed
opened 2026-02-26 10:35:33 +03:00 by kerem · 8 comments
Owner

Originally created by @c0fe on GitHub (Apr 18, 2016).
Original GitHub issue: https://github.com/PowerDNS-Admin/PowerDNS-Admin/issues/24

Ok so I have a dummy domain, adivix.org where my registrar points to my IP address as the place to check for all DNS records. So how do I properly setup the records where the DNS records are setup to point to specific servers on the local network.

Let's take this for example:

192.168.1.100 - IP Address of my DNS server
192.168.1.101 - IP Address of my website host (A record)
192.168.1.102 - IP Address of my mail server (MX record)

So how would I properly set this up so it would properly resolve to local servers on my network (all this is behind a NAT/Firewall/Router) in PowerDNS-Admin?

Originally created by @c0fe on GitHub (Apr 18, 2016). Original GitHub issue: https://github.com/PowerDNS-Admin/PowerDNS-Admin/issues/24 Ok so I have a dummy domain, adivix.org where my registrar points to my IP address as the place to check for all DNS records. So how do I properly setup the records where the DNS records are setup to point to specific servers on the local network. Let's take this for example: 192.168.1.100 - IP Address of my DNS server 192.168.1.101 - IP Address of my website host (A record) 192.168.1.102 - IP Address of my mail server (MX record) So how would I properly set this up so it would properly resolve to local servers on my network (all this is behind a NAT/Firewall/Router) in PowerDNS-Admin?
kerem 2026-02-26 10:35:33 +03:00
Author
Owner

@ngoduykhanh commented on GitHub (Apr 18, 2016):

Hi @c0fe ,

I don't understand your question. Are you asking about creating records or setting up pdns service? PowerDNS-Admin is just a Web-UI. You can create records with internal ip addresses if you want and make sure that clients are able to connect to dns server (pdns) via port 53, that's all.

<!-- gh-comment-id:211402758 --> @ngoduykhanh commented on GitHub (Apr 18, 2016): Hi @c0fe , I don't understand your question. Are you asking about creating records or setting up pdns service? PowerDNS-Admin is just a Web-UI. You can create records with internal ip addresses if you want and make sure that clients are able to connect to dns server (pdns) via port 53, that's all.
Author
Owner

@c0fe commented on GitHub (Apr 18, 2016):

I just want to correctly setup the domain via webUI where if someone externally enters "adivix.org" or sends an email what IP addresses should I enter? Public IP or the internal IP?

<!-- gh-comment-id:211411126 --> @c0fe commented on GitHub (Apr 18, 2016): I just want to correctly setup the domain via webUI where if someone externally enters "adivix.org" or sends an email what IP addresses should I enter? Public IP or the internal IP?
Author
Owner

@c0fe commented on GitHub (Apr 18, 2016):

Maybe I am doing something wrong but I keep getting 400 errors:

https://www.youtube.com/watch?v=4_8CWDmZQjw&feature=youtu.be&hd=1

<!-- gh-comment-id:211454987 --> @c0fe commented on GitHub (Apr 18, 2016): Maybe I am doing something wrong but I keep getting 400 errors: https://www.youtube.com/watch?v=4_8CWDmZQjw&feature=youtu.be&hd=1
Author
Owner

@ngoduykhanh commented on GitHub (Apr 19, 2016):

@c0fe , Do you have any error message from logfile / console ?

<!-- gh-comment-id:211665611 --> @ngoduykhanh commented on GitHub (Apr 19, 2016): @c0fe , Do you have any error message from logfile / console ?
Author
Owner

@c0fe commented on GitHub (Apr 19, 2016):

Nope, log is blank

<!-- gh-comment-id:211911281 --> @c0fe commented on GitHub (Apr 19, 2016): Nope, log is blank
Author
Owner

@ivanfilippov commented on GitHub (Apr 19, 2016):

Hi @c0fe,

Try running PowerDNS-Admin directly while we're troubleshooting instead of as a service, that will give you console access and you'll be able to show us any errors.

My guess is that PowerDNS-Admin can't connect to the PowerDNS API and that's causing the 400 error, but the console logs will show for sure.

<!-- gh-comment-id:212075109 --> @ivanfilippov commented on GitHub (Apr 19, 2016): Hi @c0fe, Try running PowerDNS-Admin directly while we're troubleshooting instead of as a service, that will give you console access and you'll be able to show us any errors. My guess is that PowerDNS-Admin can't connect to the PowerDNS API and that's causing the 400 error, but the console logs will show for sure.
Author
Owner

@ivanfilippov commented on GitHub (Jun 9, 2016):

We haven't heard from @c0fe in over a month, I think we should close this issue. What do you think @ngoduykhanh?

<!-- gh-comment-id:224778824 --> @ivanfilippov commented on GitHub (Jun 9, 2016): We haven't heard from @c0fe in over a month, I think we should close this issue. What do you think @ngoduykhanh?
Author
Owner

@ngoduykhanh commented on GitHub (Jun 9, 2016):

@ivanfilippov : Yes, I think so. Closing the issue.

<!-- gh-comment-id:224785924 --> @ngoduykhanh commented on GitHub (Jun 9, 2016): @ivanfilippov : Yes, I think so. Closing the issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/PowerDNS-Admin-PowerDNS-Admin#18
No description provided.